Windows 10: A Tale of Two Systems. What are the Lessons Learned, if any?

I have three systems at home. For my wife's system, it was kind of a "shotgun" upgrade. The system drive SSD *Mad failed without any warning, just after the warranty expired. (Mushkin, don't buy from them. *Mad ) So I had to do a clean install. A lot work to re-install everything but it went smoothly.

I use two systems, a home built desktop built around an ASUS motherboard and Intel i7 CPU and a Lenovo T530 ThinkPad. Both systems run Win 7 Pro 64. The desktop version is retail, and the laptop is OEM.

I have had no luck upgrading the desktop using the upgrade tool or downloading the software into my C: partition. Either way, I always got some bizarre error message and I never get past one reboot, and I tried 5-6 times. The laptop. It upgraded without any problems the first time this afternoon.

I've done a lot of reading on ways to get the Win 10 upgrade to work. Here's the thing. the laptop had some of the issues that supposedly prevent a successful upgrade but the laptop upgrade went start to finish, no problems:

• Don't have links to drives other than C: - I had links to drives D:, E:, and F:.
• Disconnect all drives except C:. - My system drive is on a 512 GB SSD that also has my D: and E: partitions.
• Unplug everything. - Hard to do on a laptop.
• Enlarge the System Reserved Partition to 500 MB. - Win 10 did that automatically.

So what do you guys think? I'm just tossing this out in case someone else is trying a million things to their their upgrade to work.



:)

 

A Tale of Two Computers

Hi,

I suggest you to post your query to TechNet forum for further assistance:

Technet forums - Platform Networking

Thank You.

 

A Tale of Two Computers

I have two computers running Windows 10 Pro connecting to my local network and they are nearly identical. S1 is a Lenovo T510 Core i5 560m, w/8GB memory and 500GB HD. S2 is a Lenovo W510 Core i7 820qm w/12GB memory and 750GB HD. S1 is wirelessly connected
to my LAN and S2 is connected by etherenet. Both S1 and S2 have fingerprint scanners which I use to logon. There are two other computers, both running W10 which house my network shares. S1 sees all of my network shows after initial logon with no problem.
S2 ALWAYS requires a second logon to see the network shares on only ONE of the servers; everything else shows up automatically on S2 as well as every where else. Networking is set up identically on all these computers; they are all in the same Homegroup;
network discovery and file sharing are on; they use a common workgroup name; all of them have password protection for network shares disabled, and all of them have the network identified as a private network.

I'm completely out of ideas why S2 ALWAYS requires a second logon to access the network shares on only ONE of the servers. It doesn't matter whether I log on with password, PIN or fingerprint. As fate would have it, it's the one with the most heavily
used and important shares. The odd thing is S2 always requires a 2nd provision of
S2's credentials. I wasted a lot of time figuring that out because I
thought it was asking me for credentials for the external shares. The logon prompt is ambiguous as to what credentials it is expecting me to supply. It didn't seem logical that it was asking for my S2 credentials again because I'd just supplied them
minutes, if not seconds prior. This sounds like a bug somewhere in Windows Hello or Networking. I'm not sure which. Anybody have a clue what's happening here?

 

Have you made sure your updates are current? Also, open an elevated command prompt (Right click computer and select run as administrator) in the window that opens, copy/paste this into the window sfc /scannow. It is a system file scanner and will attempt to repair any corrupted system files. You want it to come back and say 'Windows found no Integrity Violations'. If it finds errors, reboot and run it again. You may have to reboot and run it to get it to complete without errors. See if that helps.