Hi,
Can't run exe files from USB Drive.
How can I change the setting in windows 10 to be able to run it.
Regards.
New: fb2kPortable / foobar2000 (Apr 18, 2024), Platform 29.4 (Apr 10, 2024)
1,000+ portable packages, 1.1 billion downloads
Please donate today
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
It is just from the USB Drive or all EXEs no matter the location?
If it is just your USB Drive, then I really don't know. Try LiveMode?
If it is all EXEs no matter the location, then your Class for exefile got corrupted/overwritten by a malicious program. I included my copy which is clean for you to import. Taken from my Windows 10 Pro x64 (Version 1511) (Build 10586.218):
Use Notepad, Copy Paste this into it, and save it as Import.reg. Navigate to where you saved this file and import it by double clicking on it. Select Yes when prompted.
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\exefile]
@="Application"
"EditFlags"=hex:38,07,00,00
"FriendlyTypeName"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,\
00,6f,00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,\
32,00,5c,00,73,00,68,00,65,00,6c,00,6c,00,33,00,32,00,2e,00,64,00,6c,00,6c,\
00,2c,00,2d,00,31,00,30,00,31,00,35,00,36,00,00,00
[HKEY_CLASSES_ROOT\exefile\DefaultIcon]
@="%1"
[HKEY_CLASSES_ROOT\exefile\shell]
[HKEY_CLASSES_ROOT\exefile\shell\open]
"EditFlags"=hex:00,00,00,00
[HKEY_CLASSES_ROOT\exefile\shell\open\command]
@="\"%1\" %*"
"IsolatedCommand"="\"%1\" %*"
[HKEY_CLASSES_ROOT\exefile\shell\runas]
"HasLUAShield"=""
[HKEY_CLASSES_ROOT\exefile\shell\runas\command]
@="\"%1\" %*"
"IsolatedCommand"="\"%1\" %*"
[HKEY_CLASSES_ROOT\exefile\shell\runasuser]
@="@shell32.dll,-50944"
"Extended"=""
"SuppressionPolicyEx"="{F211AA05-D4DF-4370-A2A0-9F19C09756A7}"
[HKEY_CLASSES_ROOT\exefile\shell\runasuser\command]
"DelegateExecute"="{ea72d00e-4960-42fa-ba92-7792a7944c1d}"
[HKEY_CLASSES_ROOT\exefile\shellex]
[HKEY_CLASSES_ROOT\exefile\shellex\ContextMenuHandlers]
@="Compatibility"
[HKEY_CLASSES_ROOT\exefile\shellex\ContextMenuHandlers\Compatibility]
@="{1d27f844-3a1f-4410-85ac-14651078412d}"
[HKEY_CLASSES_ROOT\exefile\shellex\ContextMenuHandlers\PintoStartScreen]
@="{470C0EBD-5D73-4d58-9CED-E91E22E23282}"
[HKEY_CLASSES_ROOT\exefile\shellex\DropHandler]
@="{86C86720-42A0-1069-A2E8-08002B30309D}"
[HKEY_CLASSES_ROOT\exefile\shellex\PropertySheetHandlers]
[HKEY_CLASSES_ROOT\exefile\shellex\PropertySheetHandlers\ShimLayer Property Page]
@="{513D916F-2A8E-4F51-AEAB-0CBC76FB1AF8}"
Have an awesome day!
Jeff Savage ~ BetaLeaf
It's a global windows 10 thing... I've yet to see an answer. I have the same thing happening to me on Windows 10 Enterprise. I can't run any EXE files from external drives (regardless of formatting or permissions). I can open everything else fine, but I get a permission error when I try to run any EXE.
Not a permission issue. I've granted full control to everyone with the drive, files, etc. Nothing is working to get them to open.
It's not a Windows 10 thing. Portable apps work just fine on Windows 10. I'm using them now. It is an organization thing. If your laptop/desktop has a group policy configured to forbid running files on external drives, you can't run files on external drives. Specifically, this is the policy:
Computer > Administrative Templates > System > Removable Storage Access > Removable Disks: Deny Execute Access
Sometimes, the impossible can become possible, if you're awesome!
It is a Windows 10 thing. Windows 7 and under work fine for running executables from USB drives. What's weird is that it's specific to certain versions of Windows 10. I'm on Windows 10 Enterprise, and I can't run anything from ANY usb. However, those same usb drives work fine on my macbook's windows 10 enterprise install. It's not that policy either. I'm the tech support for my organization. I don't have any group policies in place restricting or denying access. I've read through countless sites trying to figure out what the hell is going on, and I've never figured it out. It's not anything permissions related, even though the error message says as much.