Options
Error "Windows cannot access...."
- Error "Windows cannot access...."
-
Error "Windows cannot access...."
RSable > 2021-11-08 09:27
Windows 10 Pro
Tested with virus scan disabled
QuickAccessPopup verison 11.5.2
When I try to run quickaccesspopup I get a error "windows cannot access device..." (attached error window). I tried disabling virus scan and version 11.5.1 runs fine in the same directory, If i replace it with a fresh download of 11.5.2 I get the error. If i delete all the files in the folder and reload 11.5.1 it runs fine. Neither 32 or 64 bit works with 11.5.2
![[Image: sdLvUj8.png]](https://i.imgur.com/sdLvUj8.png)
-
RE: Error "Windows cannot access...."
Jean Lalonde > 2021-11-08 12:11
Hum... I reviewed all the changes from v11.5.1 to 11.5.2 and can't see what could explain this error message. This message is displayed by Windows, not by QAP. This is why it is hard to tell what causes it.
I assume these variables are absent (or =0) in your quickaccesspopup.ini file but could you check them (under [Global] section):- DarkModeMenus
- DarkModeCustomize
- DarkModeMenus
-
RE: Error "Windows cannot access...."
RSable > 2021-11-08 14:18
(2021-11-08 12:11)Jean Lalonde Wrote: Hum... I reviewed all the changes from v11.5.1 to 11.5.2 and can't see what could explain this error message. This message is displayed by Windows, not by QAP. This is why it is hard to tell what causes it.
I assume these variables are absent (or =0) in your quickaccesspopup.ini file but could you check them (under [Global] section):- DarkModeMenus
- DarkModeCustomize
They are not in my ini file from version 11.5.1 and they don't change if I use my ini file from 11.5.1 in the 11.5.2 folder. Regardless of the ini file, if I just run the new version with no ini file, it doesn't get far enough in the install to create one. Since I can't run it with no ini file, and just create one, I'm assuming that isn't the issue. I'll be glad to check the .dll files on my system if you want me to. Just let me know which ones are being included. Also, I will download the files again in case something was corrupt. If you don't hear from me in the next 10 minutes, that didn't help.
Sorry, I forgot an important point. I'm using the portable version. I just tried it after another download and it still fails. I copied the folder to a USB drive and tried it on my work machine and it works there. Seems to be something in my home machine but I don't know where to look. - DarkModeMenus
-
RE: Error "Windows cannot access...."
joeNOR > 2021-11-08 15:33
@OP
You may want to check the Windows Event Log, typically "Application", "Security" and "System".
Also check the "Windows Defender" logs (if you use Defender), they are also in the Event Viewer.
If you want to go a bit technical, download Sysinternals Process Monitor (from Microsoft). https://docs.microsoft.com/en-us/sysinte...ds/procmon
With ProcMon you can filter on the qap exe-file to see what it does. ProcMon does generate a lot of information, and can be a little bit intimidating to use though.
Good luck!
-joeNOR -
RE: Error "Windows cannot access...."
Jean Lalonde > 2021-11-08 16:02
> if I just run the new version with no ini file, it doesn't get far enough in the install to create one. Since I can't run it with no ini file, and just create one, I'm assuming that isn't the issue.
This means that the error message occurs before QAP creates a new ini file (if it does not already exits) in the QAP initialisation sequence. There is not much happening before this point. QAP tries to create a subfolder "\_QAP_temp_nnn" under %TEMP% and copy temporary files in this folder.
> You may want to check the Windows Event Log, typically "Application", "Security" and "System".
I was going to suggest investigate in the event log but Joe is much more knowledgeable than me to guide you in this area. Thanks Joe. -
RE: Error "Windows cannot access...."
RSable > 2021-11-08 20:26
(2021-11-08 16:02)Jean Lalonde Wrote: > if I just run the new version with no ini file, it doesn't get far enough in the install to create one. Since I can't run it with no ini file, and just create one, I'm assuming that isn't the issue.
This means that the error message occurs before QAP creates a new ini file (if it does not already exits) in the QAP initialisation sequence. There is not much happening before this point. QAP tries to create a subfolder "\_QAP_temp_nnn" under %TEMP% and copy temporary files in this folder.
> You may want to check the Windows Event Log, typically "Application", "Security" and "System".
I was going to suggest investigate in the event log but Joe is much more knowledgeable than me to guide you in this area. Thanks Joe.
Jean;
Thank you for your help. I finally made an additional partition on my machine and it ran fine there, so it is obviously something in the operating system on my machine. I never would have suspected that since one version runs fine and the next one doesn't. You have a great program. I haven't got to play with it much yet but it appears to be a useful tool. Sorry to bother you with this. -
RE: Error "Windows cannot access...."
RSable > 2021-11-09 10:16
Jean;
I finally found the issue. I had shut off all the anti-virus programs (I had thought), but found out that Spectrum who provides my internet service had a program running in background that I didn't spot initially. Evidently, when I logged in to pay my bill one of the previous months they updated their online application to install some filtering and virus protection for their customers. I'm sorry you tied you up on this, but things you told me helped me to figure it out. Thanks again for everything. -
RE: Error "Windows cannot access...."
joeNOR > 2021-11-09 11:46
Very easy to overlook.....and it is a pain in the backside
I have the exact same "problem" with Windows Defender ATP and Exploit Guard.
Sometimes a process gets blocked with the same message from Windows, but no popup or toaster notification from Defender.
I have to look in the Windows Defender Event Log to see that it got blocked.
Never had this problem with QAP, but I use a couple of applications based on the Electron framework, and EVERY time they update, Defender ATP/Exploit Guard blocks them for two-three days until the central "analytical engine" at Microsoft catches up and tells Exploit Guard to let them run.
-jN