Sean Long, a Chaos Manor Reviews reader, had difficulties with the Windows 10 upgrade making his pre-Windows 7 file shares inaccessible. After much trial-and-error and incorrect information on the Googles, he figured out how to fix the problem. His solution is below. The usual precautions apply.
Thanks to Mr. Long in sharing his problem and solution. CMR is interested in similar problem-solving from CMR readers. This page has the details on how to share your solutions to computer issues. – Editor
First, if your win10 machine can’t access pre-win7 file shares (winXP, windows home server, some linux or NAS versions), go here http://bit.ly/1ZiNLdz
The original response doesn’t seem to be a complete answer, but down in the comments is the actual solution:
There is a setting in windows Local Security Policy which is incorrectly set by default for viewing an older communication protocol NAS.
To access said setting go to the Control Panel in Windows 10 (or 7), in Category view click on the text “System and Security”, then click on the text “Administrative Tools”. Now double click and open “Local Security Policy”.
In the Local Security Policy screen on the left navigation tree, expand the “Local Policies –> Security Options” then about 2/3rd’s the way down the list you’ll see a Policy called “Network Security: LAN Manager authentication level”. Double click and change the setting to be “Send LM & NTLM – use NTLMv2 session security if negotiated.”
Then just press OK and close all of the open windows and then try again.
In the case of Windows 10 Home, Local Security Policy does not exist (thanks Microsoft); therefore make the change in the registry (use the REGEDIT program). Find the indicated entry, then add a new entry as detailed below:
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.
Basically, Microsoft failed to set a critical security setting (it is set to null by default), and it needs to be set to something in order to connect to Windows XP or Windows Home Server file shares. Easy fix, stupidly hard to find though.
Second, if you have a laptop or tablet that can’t get through the Windows 10 version 1511 update, it may because you have an SD card installed. To get the Windows 10 1511 update to install correctly, you must remove the SD card before starting the update process.
If the update has failed and no longer shows as an available update, you will need to go to the Windows 10 upgrade page and re-run the Windows 10 installer. It will recognize that you already have Windows 10 installed, and will patch it to version 1511.
The critical point is to have the SD card removed throughout the entire update process. If you are like me and have moved user files to the SD card, don’t worry, it worked ok for me when I popped the SD card out right before running the installer, and put it back in before logging in after the update was complete.
Thanks to Mr. Long for his report. Enter your comments or questions below. And share your computer stories with CMR readers; start here. – Editor