"Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item."
This message began showing up two weeks ago when I would try to execute certain programs over the local network. Some programs in the directory would run, others would not. If the non-running executable was copied onto the pc, it still would not run. I downloaded new copies of the executables, they would not run. I checked for viruses, none. I checked for new programs running in memory and I did find McAfee HID, but it was not the cause. I decided to run a program directly from a host website and IT RAN.
I work in desktop support. I regularly download various setup files from all over (Quicktime, Acrobat Reader, Sun Java, etc.). To keep up with which file is the most current, when I download it, I will give it a more descriptive name if it needs it. "reaper1879-install.exe" tells me what "QuickTimeInstaller.exe" does not. I might rename the QuickTime file to "QuickTime for Windows 7.2.exe". I now know which setup version I have.
"CCleaner (Crap Cleaner) 1.41.544.exe" will not run on my computer. I get the above message. The identical file "ccsetup 141.exe" will run on my computer. If I take the first name and rename it to "1.exe", it will run.
Here are some of the names that will not run:
CCleaner (Crap Cleaner) 1.41.544.exe
CCleaner Crap Cleaner 1.41.544.exe
Here are some names that will run:
ccsetup v 1 39 502.exe
CCleaner (Crap Cleaner) 1_41_544.exe
CCleaner (Crap Cleaner) 1.41.544.setup.exe
Drive Cleaner (DCleaner) 1.08.211.setup.exe
Spybot Search and Destroy Detection Updates 2007-07-18.exe
Remote Assistance Identification 1.07-setup.exe
XnView for Windows 1.91.1.exe
QuickTime for Windows 7.2.exe
Nullsoft Install System (NSIS) 2.29.exe
I remembered an article about Vista and its permissions, which I went back and found (http://www.theregister.com/2007/04/23/vista_program_naming_oddness/
) which said,
"If Vista sees that you have created a Microsoft Visual C++ project with install in the project name, then that .exe will automatically require Admin Rights to run. Create exactly the same project, but call it, say, Fred, and the problem disappears," he explained. "Vista's security isn't just concerned with what an .exe is doing to your PC, but what it's actually called."
I suspect a Windows XP update maybe the cause of my frustrations.
What is causing the problem? (OS, AV, etc)
What are the rules for this naming convention?