Windows 10: 64-bit Windows 10 Pro build 18323 won't install - Quits at 48 percent

I cannot get these builds to install on my Dell XPS 13. This build installs to 48 percent. The last build installs to 85 percent and the one before that installs to 43 percent. I have formatted my hard drive, rolled back to 1803 hoping to remove whatever impediment that might be there and still no joy.

Any ideas?

:)

 

Can`t Upgrade 32-bit to 64-bit Windows 10

I tried upgrading my notebook/tablet pc from 32-bit to 64-bit windows 10. But it won`t boot from my usb. I checked if its compatible and followed the steps, but I didn`t get the windows "install now" option.

 

Why does 64-bit Windows 10 Pro install updates while 32-bit Windows 10 Pro upgrade from Windows 7 Pro install updates fails?

Question:

“Why does 64-bit Windows 10 Pro install updates while 32-bit Windows 10 Pro upgrade from Windows 7 Pro install updates fails?”

Issue:

"32-bit (but not 64-bit) Windows 10 Pro (Insider Preview) fails to install Microsoft updates beyond 14915"

Details:

(32-bit Fails all Updates since 14915)

• Parallels Desktop 12 for Mac created virtual machine and installed 32-bit Windows 10 Pro as free upgrade from Windows 7 Pro. After re-installing Parallels Tools and signing up for insider Preview, during the next few weeks, I installed several Windows updates
  including 14915. Each time, I also reinstalled Parallels Tools.
• When I later attempted to install update Builds (14925, 14926 and 14931) from Build 14915, the Windows 10 Pro restart crashed with a message about a stop code for "System Thread exception not handled". The system then restored the previous Build 14915.
• Faced with the threat of Windows 10 retrying updates and rebooting every 3 hours, beginning October 1, and blocking Windows 10 boot-ups, beginning October 15, I did a Windows 10 Pro reset. It deleted all system, application and user files before installing
  the clean Window 10 Pro. I also installed the Parallels Tools. When I next attempted to install the update for Build 14831, the system again crashed and restored itself to Build 14915.
• I've run the Microsoft Windows 10 Update Troubleshooter tool. It found and fixed a minor registry problem. It DID NOT solve the update crash and restoration of the previous Windows version.
• AuthorIt 5 was one of the applications used on Windows 7 that was also used on Windows 10. It could both edit and print the created documents. Researching AuthorIt, I discovered that it used the Microsoft Jet Database which is no longer supported by Microsoft.

(64-bit Continues to update normally since 14915)

• Parallels Desktop 12 for Mac created virtual machine and installed 64-bit Windows 10 Pro.
• After installing Parallels Tools and signing up for insider Preview, during the next few weeks, I installed several Windows updates (Builds 14915, 14925, 14926, 14931 and 14936) and reinstalled Parallels Tools.
• The 64-bit Microsoft Windows 10 Pro has continued to update and operate without failures.
• As of October 1, 2016, the 64-bit Windows 10 Pro is still behaving normally.
• AuthorIt 5 was one of the applications used on Windows 7 that was installed on Windows 10. It could edit but could not print the created documents. Researching
  AuthorIt, I discovered that it used the Microsoft Jet Database which is no longer supported by Microsoft.

(Possible explanation?)

• Since Authorit could never be used to Print on 64-bit Windows, I now suspect that the Jet Database was supported on the 32-bit Windows 10 only until Insider Preview Build 14915.
• Leaving AuthorIt installed on the 32-bit Windows 10 might have left a gap in the thread exception handling.

Richard S. Gordon

 

GPU-Z update loop (Windows 10 64-bit)

I don't have better steps - this is all, I have nothing to add.

Maybe it is worth noting issue was on Windows 10 Enterprise, build 14393.187, so maybe you should test on the same.
My other PCs have a different Windows 10 version - Pro, latest Insider Preview build from last week, and there is no such issue on those.
All are 64-bit edition of Windows 10.

This issue is not new. I have had same 1-2 years ago too, with older GPU-Z versions.

EDIT: And yes, I have Windows 10 UAC enabled and set to defaults. If you are using your Windows PCs with UAC off, you likely cannot reproduce this issue. *Smile