Windows 10: 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.

:)

 

Sharing drives with Win7 & Win10

My system is running both Win7 & Win10 on different SSD. There are 2 more HDDs of 2TB each in the PC. After using them in Win10 & then switch back to Win7 the 2HDDs will be scanned at bootup over & over again. Those data created in Win10 are not accessible
in Win7.

Then I got an USB flashdrive 64Gb created in Win7 & then used in Win10. After that it can't be accessed in Win7 anymore. Message say to format the drive before usage

 

invalid ip address

i'm not able to connect to pc's in lan . getting error message that drive is not accessible

 

Its not a bogus message you dont have access the reason the startup one works is because that run as system not you as a user. The simple way to get round this is to set up an account on the other pc with the same username and password as this pc as by default windows passes that to the other pc. It saves connecting AS

 

...and yet, it will eventually work, as a user, without me having
to do anything except to just wait for it...

 

...also, each PC already has each other's username and password (something
I had to do a long time ago to make them communicate)...


...also, this particular \STARTUP is under my userid and is not part of the system
(ie: under WTS)...

 

I think I FINALLY(!) circumvented these BOGUS Win10 messages!

Note that ONLY Win10 had the access problem; any other non-Win10
PC on the LAN NEVER had ANY problem accessing any files on Win10.

The key was the 'ERRORLEVEL 1231/4CFh' from both my own program,
and more importantly, from the DOS 'net view' command!!!

Searching on THAT led me to these 2 registry additions:

http://www.thetechchat.com/2015/01/2...ting-to-a-nas/
HKEY_LOCAL_MACHINE\System\CurrentControlSet\control\LSA
Add:
LMCompatibilityLevel
Value Type: REG_DWORD – Number (32 bit, hexadecimal)
Valid Range 0-5
Default: 0, Set to 1 (Use NTLMv2 session security if negotiated)
Description: This parameter specifies the type of authentication to be used.

https://community.netgear.com/t5/Usi...g/td-p/1007390
HKEY_LOCAL_MACHINE\software\microsoft\windows\currentversion\policies\system
Create a new DWORD entry with the name EnableLinkedConnections and value 1.

and these 2 DOS ADMIN commands:
sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
sc.exe config mrxsmb20 start= disabled

After a TRUE re-boot of Win10, the 'net view' command NOW works like it
should, a la Win7, even after multiple re-boots (after doing sc.exe).

So far since this, no more sporatic LAN access failures have occured.
Most notably, after the millionth tick (via WINAPI GetTickCount), when it
would start failing, until the 2nd millionth tick, when it would work again.
I guess time will tell...

So, I'm calling this the "millionth tick LAN problem".

Not sure if both are needed, but I'm SO SICK of Win10 and its 48 problems
compared to Win7 that I just wanted this HUGE accessability problem fixed!
I STILL CANNOT recommend Win10 in a productional environment; for now, it
will remain a standalone test machine. My Win7 machines are now protected
from getting the "Microsoft Trojan" (which "infects" Win7 with Win10).

 

Have you looked in to updated network drivers? We're rolling out Windows 10 in our production environment, and have been doing so for a year now. It's very easy to recommend for production because it works very well. The funny thing is, if Windows 10 was the issue, all of us using it would be experiencing these "48 problems". Too few people realize that there are many third-party variables that go in to a system/network, etc. If 10 was so bad, these issues would be repeatable.

 

Well said, Deacon! I not only say "Amen" I also blogged about this very topic Monday: The Long Win10 Tail Carries a Nasty Barb - Windows Enterprise Desktop. Enjoy!
--Ed--