New
#71
There are third party software that can perform preliminary debugging: whocrashed, bluescreenview.
The tool that we use is windbg.
It provides deeper debugging.
Multiple commands can be ran to find misbehaving drivers.
There are third party software that can perform preliminary debugging: whocrashed, bluescreenview.
The tool that we use is windbg.
It provides deeper debugging.
Multiple commands can be ran to find misbehaving drivers.
It's still rock solid as it always is. No hang, no BSD, no restart.
Once misbehaving drivers can be ruled in or ruled out the environment may be better for an upgrade.
Whenever you have time the tool can be turned on to see the status of the drivers with stress testing.
FIXED
I noticed that the Windows 10 Upgrade folder creates 2 ESD files for some strange reason, both named the same except for an underscore at the end of one. They are exactly the same files with the same hashes, so I converted one of those ESDs to ISO using ESD Decrypter and mounted it, and it worked.
After months of trying off and on, converting one of the ESDs found in the Windows10Upgrade folder to ISO that is produced from running Microsoft's Windows 10 Upgrade Tool, then mounting it, I have finally had success.
Something that I have noticed immediately, is that the ISO produced from converting the ESD is much larger than the ISO you get from Microsoft's Media Creation Tool.
I hope this may help anyone else with the same or similar problem.
Everything seems to be working. The Device Manager is all clear of problems.
Who would have thought? The strange enigma called "Windows".
Download Windows 10 (Includes Microsoft's Windows 10 Upgrade Tool & Media Creation Tool)
Why the existing ESDs failed every time, but worked when converted to ISO, I do not know.
Someone smarter than me can try and work that one out.
Thanks for your help, zbook.
You are very welcome.
The credit is yours for the ingenuity of the last step.
What link is available that has the steps?
That was great work!
Had you used esd decrypter before?
Please post an updated beta zip into the thread.
Yes, I've used various versions of ESD Decrypter before, but not for this purpose, and I didn't grab the ESD from the Windows10Upgrade Folder before now. But when I noticed two ESDs exactly the same apart from the underscore, it just made me wonder why. So, that's when I thought I would try converting one to ISO and mounting and running it that way.
Attached is the ESD Decrypter that I used. Put the ESD in the ESD folder inside ESD Decrypter, and run decrypt.cmd. I put the ESD folder at the root of my backup D drive to avoid any long path problems that may occur. Not sure if they would.
It converted the 3.23 GB ESD to a 4.55 GB x64 multi-version ISO.
I'm saving it.