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

Page 1 of 2 12 LastLast

  1. Posts : 1,750
    Windows 10 Pro
       #1

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


    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
      My Computers


  2. Posts : 5,452
    windows 10 Pro ver 21H2 build 19044.1348
       #2

    Wouldn't it be best for you if you asked the experts of Windows 7 at Windows 7 forum ?

    Please use this link to our 7 forum :
    http://www.sevenforums.com/
      My Computer


  3. Posts : 16,325
    W10Prox64
       #3

    Hi.
    You can open the setuperr.log in notepad and have a look at the error codes, and start Googling them one by one. That's what I do.
      My Computer


  4. Posts : 1,750
    Windows 10 Pro
    Thread Starter
       #4

    davidhk said:
    Wouldn't it be best for you if you asked the experts of Windows 7 at Windows 7 forum ?

    Please use this link to our 7 forum :
    http://www.sevenforums.com/
    OK, I will do that. Thanks.

    x509
      My Computers


  5. Posts : 1,750
    Windows 10 Pro
    Thread Starter
       #5

    simrick said:
    Hi.
    You can open the setuperr.log in notepad and have a look at the error codes, and start Googling them one by one. That's what I do.
    I have been doing that, but the results have been surprisingly unhelpful. That's why I posted this question. If I get a BSOD for example, and I google the code, I get good specific results and I know just what to do.

    Just for grins I looked at the setuperr.log file on my Lenovo laptop, which upgraded to Win 10 Pro 64 no problems first time. That setuperr.log file was also 64 KB, and was filled with the same kinds of errors as the setuperr.log file on my desktop where the Win 10 upgrade failed.

    Thank you Microsoft.
      My Computers


  6. Posts : 16,325
    W10Prox64
       #6

    x509 said:
    I have been doing that, but the results have been surprisingly unhelpful. That's why I posted this question. If I get a BSOD for example, and I google the code, I get good specific results and I know just what to do.

    Just for grins I looked at the setuperr.log file on my Lenovo laptop, which upgraded to Win 10 Pro 64 no problems first time. That setuperr.log file was also 64 KB, and was filled with the same kinds of errors as the setuperr.log file on my desktop where the Win 10 upgrade failed.

    Thank you Microsoft.
    Why don't you post it here and we can have a look?
    Where did the upgrade fail on your desktop (at what point)?
      My Computer


  7. Posts : 1,750
    Windows 10 Pro
    Thread Starter
       #7

    simrick said:
    Why don't you post it here and we can have a look?
    Where did the upgrade fail on your desktop (at what point)?
    The entire 64 KB file???

    I wasn't watching my display the entire time the upgrade was proceeding, so I'll repeat the upgrade and post the setuperr.log from that upgrade once I know the right way to do that. The last setuperr.log file was 305 lines. I know that because I imported that file into Excel.
      My Computers


  8. Posts : 16,325
    W10Prox64
       #8

    x509 said:
    The entire 64 KB file???
    Yeah, probably upload to onedrive/dropbox/pastebin, etc. and provide link.

    x509 said:
    I wasn't watching my display the entire time the upgrade was proceeding, so I'll repeat the upgrade and post the setuperr.log from that upgrade once I know the right way to do that. The last setuperr.log file was 305 lines. I know that because I imported that file into Excel.
    Okay, if you haven't started yet:

    You said SFC /SCANNOW completed with "no integrity violations found", right?

    Uninstall the Comcast/Norton AV; also any HDD/system monitoring programs (i.e. Speccy)
    If you've moved your libraries, move them back (just the pointers for now, not the data)
    Disconnect all HDDs except OS
    Disconnect all peripherals except mouse, keyboard and monitor (use wired if you can)

    Download the Media Creation Tool; make an ISO; save to desktop. Use 7-Zip to extract the files to desktop. Double-click setup.exe to begin the upgrade.

    (Ref. tutorial here Windows 10 - Upgrade Installation - Windows 10 Forums )

    Pay attention at what point it fails - there are three parts:


    How to interpret setupact.log and setuperr.log from failed W10 install-upgrade-3parts.png

    If it's a failure during the first part, it's usually drivers. If it fails right at the very end, it's usually because it failed to make the recovery "go back".
      My Computer


  9. Posts : 1,750
    Windows 10 Pro
    Thread Starter
       #9

    simrick said:
    Yeah, probably upload to onedrive/dropbox/pastebin, etc. and provide link.



    Okay, if you haven't started yet:

    You said SFC /SCANNOW completed with "no integrity violations found", right?

    Uninstall the Comcast/Norton AV; also any HDD/system monitoring programs (i.e. Speccy)
    If you've moved your libraries, move them back (just the pointers for now, not the data)
    Disconnect all HDDs except OS
    Disconnect all peripherals except mouse, keyboard and monitor (use wired if you can)

    Download the Media Creation Tool; make an ISO; save to desktop. Use 7-Zip to extract the files to desktop. Double-click setup.exe to begin the upgrade.

    (Ref. tutorial here Windows 10 - Upgrade Installation - Windows 10 Forums )

    Pay attention at what point it fails - there are three parts:


    How to interpret setupact.log and setuperr.log from failed W10 install-upgrade-3parts.png

    If it's a failure during the first part, it's usually drivers. If it fails right at the very end, it's usually because it failed to make the recovery "go back".
    All good stuff. I will have to open up my system unit and unplug a bunch of cables, etc, plus do some software uninstalls, etc, so I might not get to this before the weekend, but I am HIGHLY motivated.

    I really appreciate this.
    I only hope I can give back to all the other guys on this board as much.
      My Computers


  10. Posts : 16,325
    W10Prox64
       #10

    x509 said:
    All good stuff. I will have to open up my system unit and unplug a bunch of cables, etc, plus do some software uninstalls, etc, so I might not get to this before the weekend, but I am HIGHLY motivated.

    I really appreciate this.
    I only hope I can give back to all the other guys on this board as much.
    No problem. Take your time. We'll be around.
      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 04:17.
Find Us




Windows 10 Forums