New
#1
Win10 creates BOGUS message when accessing PC on LAN
FYI:
I have found that, after a TRUE re-boot (not Hibernate), when I
try to access another PC via my wired LAN via explorer, I get this
BOGUS message window:
Windows cannot access xxx
It is BOGUS because one of my own programs also accesses a file
across the LAN to that same machine, started via \STARTUP, and it
has no problem. For example, if I use explorer a few minutes, 10,
or even an hour after I re-boot, while my program has been running
successfully for that entire time (it accesses a file once per
minute), I may STILL get this BOGUS msg from explorer. This problem
never occurs in Win7 unless, in an open explorer window, the other
machine is powered off after it was accessed.
However, if I X that BOGUS window, slowly count to 20, then try
it again, it MAY work fine, or, even after MANY MULTIPLE ATTEMPTS,
seemingly require ANOTHER TRUE re-boot to get access back!!!
Then, if I just close explorer and re-open it, it may start this
garbage all over again! HORRIBLE!
This is not CPU-related, as CPUR is 100% for only about 5 seconds.
Afterwards, it averages apx 60% for the next minute (btx 30-90%).
Measured and logged via WTS every 5 seconds, which is started even
before any logon, and thus, explorer, is issued.