A formerly working Windows 10 program, that I compiled & have rights to, now cannot be run or copied, even on a different Windows 10 PC

D

DrBob_Miller

I am a software developer, working on small test programs at the moment. A program I had gotten to compile and run, suddenly developed a problem that made Windows not allow it to run anymore. That is, the same source code that had successfully run before, and which still compiles without errors, will not run now.


When I try to run it, I get error messages like these:

  • "Another program is currently using this file"
  • Or "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item."
  • Or "Unable to create process: access is denied" if I try to run it in the IDE


Windows File Explorer will not let me copy the exe file to a thumb drive, to try it on a different computer.


Beyond Compare did let me copy to a thumb drive, so I copied this file to another Windows 10 computer. When I try to run the exe file there, I sometimes get the message "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item," and sometimes get "Another program is currently using this file."


I have searched the web for ways to fix this, but none of them work, or even show any clues.

  • Checking File Explorer's View | Options | Change folder and search options shows that item "Launch folder windows in a separate process" isn't checked and changing this does not make any difference.
  • Resource Monitor cannot find any process that owns this file
  • Process Monitor cannot find any process that owns this file
  • Power Shell method cannot find any process that owns this file

People have complained about this Windows problem for a long time, which is why there are so many articles claiming to have ways to fix a problem like this.


Because Windows claims that "Another program is currently using this file," even when I try to run this program on a different PC, this means that there is some setting that is buried somewhere in the EXE file itself.


This is long standing, bad behavior by Windows 10 itself. How can I fix this, and how can I prevent this from happening again ???


Please help.

Continue reading...
 
Back
Top Bottom