How to interpret setupact.log and setuperr.log from failed W10 install

Page 2 of 2 FirstFirst 12

  1. Posts : 1,770
    Windows 10 Pro
    Thread Starter
       #11

    Simrick and everyone else,

    After considerable time spent going down several rabbit holes (and a lot of travel for my job), I got serious again about doing this Win 10 upgrade. First time, same flameout at 22%, but with a different error message this time. 0x800703f1-0x2000a. Doing some searching, I kept on getting links for registry corruption.

    So I spent time trying out different registry cleaners. Then I installed the free version of CCleaner. Wowzers. Almost 1400 issues, way more than any of those not-free registry cleaners. In a way not surprising, since this Windows 7 image has been in service since early 2012 and I've gone through many software installs, uninstalls, upgrades, trials, you-name-it.

    After running CCleaner, I was successful with the Win 10 upgrade. Woohoo! I'm happy. The sun is shining again. Time to change my sig.

    x509.
      My Computers


  2. Posts : 7,901
    Windows 11 Pro 64 bit
       #12

    x509 said:
    Are there any tools that help pinpoint the real errors as opposed to all the "noise".

    My setuperr file is "only" 65KB but the setupact file is, and I'm not making this up, 32,866 KB. Is a setupact file that big a "good thing" or a "really, really bad thing?"



    I'm asking becuase the error messages from Windows are useful to identify the issues.

    Following a suggestion from an earlier reply in one of my threads, I ran sfc /scannow, and the result was no issues.

    Thanks,

    x509
    I had a similar problem and just searched for the errors at the end of the file which caused the installation to fail. I discovered my problem was due to a corrupted EFI system partition. The PC would boot fine in Windows 8.1 but the corruption caused the Windows 10 installation to fail.
      My Computers


  3. Posts : 16,325
    W10Prox64
       #13

    x509 said:
    Simrick and everyone else,

    After considerable time spent going down several rabbit holes (and a lot of travel for my job), I got serious again about doing this Win 10 upgrade. First time, same flameout at 22%, but with a different error message this time. 0x800703f1-0x2000a. Doing some searching, I kept on getting links for registry corruption.

    So I spent time trying out different registry cleaners. Then I installed the free version of CCleaner. Wowzers. Almost 1400 issues, way more than any of those not-free registry cleaners. In a way not surprising, since this Windows 7 image has been in service since early 2012 and I've gone through many software installs, uninstalls, upgrades, trials, you-name-it.

    After running CCleaner, I was successful with the Win 10 upgrade. Woohoo! I'm happy. The sun is shining again. Time to change my sig.

    x509.
    Great news! Yeah, Ccleaner is the best. So glad you got it upgraded. Cheers and thanks for posting back with your solution. :)

    EDIT: Please go ahead and mark the thread as solved.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:09.
Find Us




Windows 10 Forums