Windows 10: 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,



:)

 

Interpreting SetupErr.Log

We appreciate the information that you've provided. The error codes that you've received mostly occurs when you lack file or registry permissions that are required to install the update. To address these error codes, you may check the articles below:

• Error 0x80070005
  in Windows Update when you try to install updates
  
• Error code
  0x8007000D when trying to activate a Windows server

Note: The troubleshooting steps provided in the links above are also applicable to Windows 10 devices.


Feel free to post back for an update and let us know if you need more help.

 

windows 10 upgrade is failing already 9 times

My Winodws 10 upgrade from Windows 7 Ultimate always fails at 91% while installing in the fullscreen purple installer from the media creation tool. I also tried to update via Windows update and from CD. The error log in C:\$Windows.~BT\Sources\Panther\setuperr.log
shows this information: setuperr.log

http://thetechtrick.net/setupact.log

Can anyone help me solving this issue? When you need more data just ask.

 

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 :
Windows 7 Help Forums

 

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.

 

OK, I will do that. Thanks.

 

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. *Banghead

Thank you Microsoft. *cry

 

*Wink 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.

 

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:






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.

 

No problem. Take your time. We'll be around.

 

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. *Devil

So I spent time trying out different registry cleaners. *Sick Then I installed the free version of CCleaner. Wowzers. Almost 1400 issues, way more than any of those not-free registry cleaners.*really 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!*Party *Party I'm happy. The sun is shining again. Time to change my sig.

.

 

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.

 

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

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