Windows 10: UserProfileCreationFailureDuringFinalize

Hi I'm attempting to upgrade a Dell Precision 5510 with Windows 7pro to 10pro and it gets to the first reboot and then fails.

When I run setupdiag, I get the following. I don't have any unused profiles, so I don't know what steps next I can do to troubleshoot.



Matching Profile found: UserProfileCreationFailureDuringFinalize - C6677BA6-2E53-4A88-B528-336D15ED1A64

SetupDiag version: 1.6.0.0

System Information:

Machine Name = vadaba Manufacturer = Dell Inc. Model = Precision 5510 HostOSArchitecture = x64 FirmwareType = UEFI BiosReleaseDate = 20200723000000.000000+000 BiosVendor = BIOS Date: 07/23/20 06:12:08 Ver: [1.15.0.00](https://1.15.0.00) BiosVersion = 1.15.0 HostOSVersion = 6.1.7601 HostOSBuildString = 7601.24545.amd64fre.win7sp1\_ldr\_escrow.200102-1707 TargetOSBuildString = 10.0.19041.621 (vb\_release\_svc\_prod1.201014-1758) HostOSLanguageId = HostOSEdition = Professional RegisteredAV = FilterDrivers = FileInfo UpgradeStartTime = 3/19/2021 3:43:42 PM UpgradeEndTime = 3/19/2021 6:13:01 PM UpgradeElapsedTime = 02:29:19 CV = ReportId =





Error: SetupDiag reports user profile creation failure during Finalize.

Last Phase: Finalize

Last Operation: Gather data, scope: EVERYTHING

Error = 32.

Recommend you check for unused user profiles and remove any unnecessary profiles found. Reboot and try the update again.



Last Setup Phase:

Phase Name: Finalize

Phase Started: 3/19/2021 6:06:33 PM Phase Ended: 1/1/0001 12:00:00 AM Phase Time Delta: 00:00:00 Completed Successfully? False





Last Setup Operation:

Operation Name: Gather data, scope: EVERYTHING

Operation Started: 3/19/2021 6:10:35 PM Operation Ended: 1/1/0001 12:00:00 AM Operation Time Delta: 0:00:00:00.0000000 Completed Successfully? False
submitted by /u/SushiX2000
[link] [comments]

:)

 

Need Suggestions for a failed 1809 update

Guess I should have mentioned that I did do that. I just reran it for this post. I'm not sure which update attempt this was (e.g. had I disconnected my wireless usb mouse? was AV disabled?).

The summary and console are below. I took those results to indicate setupdiag didn't find anything. But I didn't realize it had generated that zip although I'm not sure how to read that.


Code:

 

Battery icon disappearing from taskbar

Just a quick update to what I've done so far in case that saves you any additional work. (When I started this, I didn't realize it would be so long. I apologize if this is TMI. ).

Going down the Quick Fixes:

1. I don't have anything plugged into my laptop except power. No docking station, etc.

2. Repair System Drive - chkdsk /f worked. 100% pass

3. Windows Update Troubleshooter - We did that already (SetupDiag.exe)

4. Repair System Files - sfc /scannow and DISM.exe /Online /Cleanup-image /Restorehealth both worked. No problems.

5. Update Windows - I checked yesterday and it said I was up to date, but they recommend v1903. Today I rechecked and this time it downloaded and now I see this:





So it apparently downloaded and is now Pending install??? It hasn't asked me to start that yet and I'm not going to do anything to start it. I did go to the Microsoft Website and I downloaded the Standalone Package. So I have that file on my C:\Users\v015e\Downloads\
folder now.

6. Uninstall non-Microsoft antivirus software - Would prefer not to do this just yet. I have done at least one Windows Update successfully since I got this PC in March and had no problems then.

7. Uninstall non-Essential Software - I don't have any non-Essential Software. I don't believe I have installed anything since the last successful Windows Update except maybe Kindle app.

8. Update Firmware and Drivers - You mentioned my BIOS was OK. I just did a driver check and it says I'm fine:





8. Ensure that "Download and install updates" is selected - Will do that if/when prompted.

9. Verify Disk Space - I have plenty





10. Open an elevated command prompt - It says this is the optimal way to run the SetupDiag tool. So I did. I ran the one I ran yesterday, which is in a subfolder of the Downloads folder. This time it showed no failure:

C:\Users\v015e\Downloads\SetupDiag>SetupDiag

SetupDiag v1.6.0.0

Copyright (c) Microsoft Corporation. All rights reserved.

Searching for setup logs...

Found C:\$WINDOWS.~BT\Sources\Panther\setupact.log with update date 9/7/2019 9:15:19 AM to be the correct setup log.

Gathering baseline information from setup logs...

SetupDiag: processing rule: CompatScanOnly.

...No match.

SetupDiag: processing rule: PlugInComplianceBlock.

...No match.

SetupDiag: processing rule: BitLockerHardblock.

...No match.

SetupDiag: processing rule: VHDHardblock.

...No match.

SetupDiag: processing rule: PortableWorkspaceHardblock.

...No match.

SetupDiag: processing rule: AuditModeHardblock.

...No match.

SetupDiag: processing rule: SafeModeHardblock.

...No match.

SetupDiag: processing rule: InsufficientSystemPartitionDiskSpaceHardblock.

...No match.

SetupDiag: processing rule: CompatBlockedApplicationAutoUninstall.

...No match.

SetupDiag: processing rule: CompatBlockedApplicationDismissable.

...No match.

SetupDiag: processing rule: CompatBlockedApplicationManualUninstall.

...No match.

SetupDiag: processing rule: HardblockDeviceOrDriver.

...No match.

SetupDiag: processing rule: HardblockMismatchedLanguage.

..No match.

SetupDiag: processing rule: HardblockFlightSigning.

..No match.

SetupDiag: processing rule: DiskSpaceBlockInDownLevel.

..No match.

SetupDiag: processing rule: DiskSpaceFailure.

..No match.

SetupDiag: processing rule: PreReleaseWimMountDriverFound.

..No match.

SetupDiag: processing rule: DeviceInstallHang.

...No match.

SetupDiag: processing rule: BootFailureDetected.

.No match.

SetupDiag: processing rule: WinSetupBootFilterFailure.

..No match.

SetupDiag: processing rule: FindDebugInfoFromRollbackLog.

.No match.

SetupDiag: processing rule: AdvancedInstallerFailed.

..No match.

SetupDiag: processing rule: AdvancedInstallerGenericFailure.

..No match.

SetupDiag: processing rule: FindMigApplyUnitFailure.

..No match.

SetupDiag: processing rule: FindMigGatherUnitFailure.

..No match.

SetupDiag: processing rule: FindMigGatherApplyFailure.

..No match.

SetupDiag: processing rule: OptionalComponentFailedToGetOCsFromPackage.

..No match.

SetupDiag: processing rule: OptionalComponentOpenPackageFailed.

..No match.

SetupDiag: processing rule: OptionalComponentInitCBSSessionFailed.

..No match.

SetupDiag: processing rule: CriticalSafeOSDUFailure.

..No match.

SetupDiag: processing rule: UserProfileCreationFailureDuringOnlineApply.

..No match.

SetupDiag: processing rule: UserProfileCreationFailureDuringFinalize.

..No match.

SetupDiag: processing rule: WimMountFailure.

..No match.

SetupDiag: processing rule: WimMountDriverIssue.

..No match.

SetupDiag: processing rule: WimApplyExtractFailure.

..No match.

SetupDiag: processing rule: UpdateAgentExpanderFailure.

.No match.

SetupDiag: processing rule: FindFatalPluginFailure.

..No match.

SetupDiag: processing rule: MigrationAbortedDueToPluginFailure.

..No match.

SetupDiag: processing rule: DISMAddPackageFailed.

..No match.

SetupDiag: processing rule: DISMImageSessionFailure.

..No match.

SetupDiag: processing rule: DISMproviderFailure.

..No match.

SetupDiag: processing rule: SysPrepLaunchModuleFailure.

..No match.

SetupDiag: processing rule: UserProvidedDriverInjectionFailure.

..No match.

SetupDiag: processing rule: FindSuccessfulUpgrade.

..No match.

SetupDiag: processing rule: FindSetupHostReportedFailure.

..No match.

SetupDiag: processing rule: FindDownlevelFailure.

..No match.

SetupDiag: processing rule: FindAbruptDownlevelFailure.

..No match.

SetupDiag: processing rule: FindEarlyDownlevelError.

..No match.

SetupDiag: processing rule: FindSPFatalError.

..No match.

SetupDiag: processing rule: FindSetupPlatformFailedOperationInfo.

..No match.

SetupDiag: processing rule: FindRollbackFailure

..No match.

SetupDiag found 0 matching issue.

Logs ZipFile created at: .\Logs_1.zip

C:\Users\v015e\Downloads\SetupDiag>

I also ran the one in the root Download folder and the log says the same thing:

SetupDiag was unable to match to any known failure signatures.

System Information:

Machine Name = LAPTOP-CAV6EM4G

Manufacturer = LENOVO

Model = 81H7

HostOSArchitecture = 1033

FirmwareType = UEFI

BiosReleaseDate = 20190515000000.000000+000

BiosVendor = 8QCN19WW(V1.07)

BiosVersion = 8QCN19WW(V1.07)

HostOSVersion = 10.0.17134

HostOSBuildString = 17134.1.amd64fre.rs4_release.180410-1804

TargetOSBuildString = 10.0.18362.323 (19h1_release_svc_prod2.190809-2149)

HostOSLanguageId =

HostOSEdition = Core

RegisteredAV = Norton 360

FilterDrivers =

UpgradeStartTime = 9/7/2019 9:14:17 AM

UpgradeEndTime = 9/7/2019 9:15:19 AM

UpgradeElapsedTime = 00:01:02

CV = vqHJFCAtq0G+VEcG

ReportId = DDF6F37D-C199-452C-8A51-ACD81277B663

 

How to troubleshoot setupdiag flash

Microsoft setupdiag software is used to troubleshoot failure to upgrade Windows.

https://docs.microsoft.com/en-us/win...rade/setupdiag

Clicking on the download setupdiag link after download displays choices for open or save.

Clicking on open > displays a flash and no setupdiag results

Clicking on save > right click on setupdiag > run as administrator displayed the first time the results in the administrative command prompt box and an immediate close. There was no time to look at the post except that it had found 1 item.
All additional run as administrator displayed flashes with no setupdiag results

The setupdiag software had been run earlier this year.
And there are old log files with results.

Changing the directory altered the flash.

These were the results from March 2019

Code:

These were the results from September 2019:

Code:

All setupdiag runs now display a flash.
Changing the directory produces results within the administrative command prompt box that are visible without an immediate close after it completes the results:


Code:

The results that were displayed were dated March 2019.

The March 2019 results had displayed no problem in the earlier code box.
The September 2019 results had displayed a problem in the earlier code box.
Somehow the software has scanned the March 2019 panther logs and displayed problems from September?

How come the setupdiag software does not work properly without changing the directory?


Code:

Running setupdiag in clean boot or safe mode did not change the flash.
Only changing the directory changed the flash.



How do you troubleshoot the directory problem so that the link in
https://docs.microsoft.com/en-us/win...rade/setupdiag
can be clicked and it runs the software without a flash and displays results without having to change the directory?