How to troubleshoot setupdiag flash


  1. zbook
    Posts : 39,996
    windows 10 professional version 1607 build 14393.969 64 bit
       New #1

    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:
    Matching Profile found: FindSuccessfulUpgrade - 8A0824C8-A56D-4C55-95A0-22751AB62F3E
SetupDiag version: 1.6.0.0
System Information:
	Machine Name = DESKTOP-K2CP43S
	Manufacturer = Hewlett-Packard
	Model = HP ZBook 17
	HostOSArchitecture = 1033
	FirmwareType = PCAT
	BiosReleaseDate = 20180808000000.000000+000
	BiosVendor = Default System BIOS
	BiosVersion = L70 Ver. 01.44
	HostOSVersion = 10.0.17134
	HostOSBuildString = 17134.1.amd64fre.rs4_release.180410-1804
	TargetOSBuildString = 10.0.17763.345 (rs5_release_svc_prod2.190213-1831)
	HostOSLanguageId = 
	HostOSEdition = Professional
	RegisteredAV = Windows Defender
	FilterDrivers = FileInfo
	UpgradeStartTime = 3/17/2019 10:57:24 PM
	UpgradeEndTime = 3/18/2019 1:53:16 AM
	UpgradeElapsedTime = 02:55:52
	CV = UTf0JYTro02g0srw
	ReportId = 82DD3C30-D6F9-4FB5-94E9-3B896CFC20C2


SetupDiag reports successful upgrade found.
This appears to be a successful update as the last operation was: OOBEBoot and the result was: success

Last Setup Phase:
Phase Name: End
	Phase Started: 3/18/2019 1:50:19 AM
	Phase Ended: 3/18/2019 1:50:19 AM
	Phase Time Delta: 00:00:00
	Completed Successfully? True


Last Setup Operation:
Operation Name: Start suspended services
	Operation Started: 3/18/2019 1:49:50 AM
	Operation Ended: 3/18/2019 1:49:53 AM
	Operation Time Delta: 0:00:00:03.0000000
	Completed Successfully? True


Matching Profile found: FindSuccessfulUpgrade - 8A0824C8-A56D-4C55-95A0-22751AB62F3E
SetupDiag version: 1.6.0.0
System Information:
	Machine Name = DESKTOP-K2CP43S
	Manufacturer = Hewlett-Packard
	Model = HP ZBook 17
	HostOSArchitecture = 1033
	FirmwareType = PCAT
	BiosReleaseDate = 20180808000000.000000+000
	BiosVendor = Default System BIOS
	BiosVersion = L70 Ver. 01.44
	HostOSVersion = 10.0.17134
	HostOSBuildString = 17134.1.amd64fre.rs4_release.180410-1804
	TargetOSBuildString = 10.0.17763.345 (rs5_release_svc_prod2.190213-1831)
	HostOSLanguageId = 
	HostOSEdition = Professional
	RegisteredAV = Windows Defender
	FilterDrivers = FileInfo
	UpgradeStartTime = 3/17/2019 10:57:24 PM
	UpgradeEndTime = 3/18/2019 1:53:16 AM
	UpgradeElapsedTime = 02:55:52
	CV = UTf0JYTro02g0srw
	ReportId = 82DD3C30-D6F9-4FB5-94E9-3B896CFC20C2


SetupDiag reports successful upgrade found.
This appears to be a successful update as the last operation was: OOBEBoot and the result was: success

Last Setup Phase:
Phase Name: End
	Phase Started: 3/18/2019 1:50:19 AM
	Phase Ended: 3/18/2019 1:50:19 AM
	Phase Time Delta: 00:00:00
	Completed Successfully? True


Last Setup Operation:
Operation Name: Start suspended services
	Operation Started: 3/18/2019 1:49:50 AM
	Operation Ended: 3/18/2019 1:49:53 AM
	Operation Time Delta: 0:00:00:03.0000000
	Completed Successfully? True


Matching Profile found: FindSuccessfulUpgrade - 8A0824C8-A56D-4C55-95A0-22751AB62F3E
SetupDiag version: 1.6.0.0
System Information:
	Machine Name = DESKTOP-K2CP43S
	Manufacturer = Hewlett-Packard
	Model = HP ZBook 17
	HostOSArchitecture = 1033
	FirmwareType = PCAT
	BiosReleaseDate = 20180808000000.000000+000
	BiosVendor = Default System BIOS
	BiosVersion = L70 Ver. 01.44
	HostOSVersion = 10.0.17134
	HostOSBuildString = 17134.1.amd64fre.rs4_release.180410-1804
	TargetOSBuildString = 10.0.17763.345 (rs5_release_svc_prod2.190213-1831)
	HostOSLanguageId = 
	HostOSEdition = Professional
	RegisteredAV = Windows Defender
	FilterDrivers = FileInfo
	UpgradeStartTime = 3/17/2019 10:57:24 PM
	UpgradeEndTime = 3/18/2019 1:53:16 AM
	UpgradeElapsedTime = 02:55:52
	CV = UTf0JYTro02g0srw
	ReportId = 82DD3C30-D6F9-4FB5-94E9-3B896CFC20C2


SetupDiag reports successful upgrade found.
This appears to be a successful update as the last operation was: OOBEBoot and the result was: success

Last Setup Phase:
Phase Name: End
	Phase Started: 3/18/2019 1:50:19 AM
	Phase Ended: 3/18/2019 1:50:19 AM
	Phase Time Delta: 00:00:00
	Completed Successfully? True


Last Setup Operation:
Operation Name: Start suspended services
	Operation Started: 3/18/2019 1:49:50 AM
	Operation Ended: 3/18/2019 1:49:53 AM
	Operation Time Delta: 0:00:00:03.0000000
	Completed Successfully? True

    These were the results from September 2019:

    Code:
    Matching Profile found: FindSetupHostReportedFailure - 6253C04F-2E4E-4F7A-B88E-95A69702F7EC
System Information:
	Machine Name = DESKTOP-K2CP43S
	Manufacturer = Hewlett-Packard
	Model = HP ZBook 17
	HostOSArchitecture = x64
	FirmwareType = PCAT
	BiosReleaseDate = 20170713000000.000000+000
	BiosVendor = Default System BIOS
	BiosVersion = L70 Ver. 01.37
	HostOSVersion = 10.0.17134
	HostOSBuildString = 17134.1.amd64fre.rs4_release.180410-1804
	TargetOSBuildString = 10.0.17134.1 (rs4_release.180410-1804)
	HostOSLanguageId = 1033
	HostOSEdition = Professional
	RegisteredAV = 
	FilterDrivers = 
	UpgradeStartTime = 9/29/2018 1:18:48 AM
	UpgradeEndTime = 9/29/2018 1:21:59 AM
	UpgradeElapsedTime = 00:03:11
	ReportId = 5dea7991-c222-4f52-8fe3-6c3758e7a330

Error: SetupDiag reports down-level failure, Operation: Finalize, Error: 0x800704C7 - 0x4001B
Refer to https://docs.microsoft.com/en-us/windows/deployment/upgrade/upgrade-error-codes for error information.

Matching Profile found: FindSuccessfulUpgrade - 8A0824C8-A56D-4C55-95A0-22751AB62F3E
System Information:
	Machine Name = DESKTOP-K2CP43S
	Manufacturer = Hewlett-Packard
	Model = HP ZBook 17
	HostOSArchitecture = x64
	FirmwareType = PCAT
	BiosReleaseDate = 20180808000000.000000+000
	BiosVendor = Default System BIOS
	BiosVersion = L70 Ver. 01.44
	HostOSVersion = 10.0.17134
	HostOSBuildString = 17134.1.amd64fre.rs4_release.180410-1804
	TargetOSBuildString = 10.0.17763.345 (rs5_release_svc_prod2.190213-1831)
	HostOSLanguageId = 1033
	HostOSEdition = Professional
	RegisteredAV = 
	FilterDrivers = 
	UpgradeStartTime = 3/17/2019 10:57:24 PM
	UpgradeEndTime = 3/18/2019 1:53:16 AM
	UpgradeElapsedTime = 02:55:52
	ReportId = 82DD3C30-D6F9-4FB5-94E9-3B896CFC20C2

SetupDiag reports successful upgrade found.
This appears to be a successful update as the last operation was: OOBEBoot and the result was: success

    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:
    C:\>cd users\a

C:\Users\a>cd downloads

C:\Users\a\Downloads>setupdiag

SetupDiag v1.6.0.0
Copyright (c) Microsoft Corporation. All rights reserved.

Searching for setup logs...
Found C:\Windows\Panther\setupact.log with update date 3/18/2019 1:53:16 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.
..
SetupDiag reports successful upgrade found.
This appears to be a successful update as the last operation was: OOBEBoot and the result was: success

SetupDiag found 1 matching issue.

SetupDiag results were logged to: .\SetupDiagResults.log
Logs ZipFile created at: .\Logs_2.zip

C:\Users\a\Downloads>

    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:
    C:\>cd users\a

C:\Users\a>cd downloads

C:\Users\a\Downloads>setupdiag


    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?
    Last edited by zbook; 16 Oct 2019 at 20:08.
      My Computer
    Quote Quote

 

  Related Discussions
Flash is installed but all flash embeds are replaced with blue i information icon. And I am using a web browser called Basilisk that supports flash. Is a windows update by microsoft blocking the flash player from running? Why is this happening? ...
When running SetupDiag.exe, after another failed 1803 update, the log file shows entries like the below. Q: What does this 'No Match' mean? Thanks. SetupDiag: processing rule: CompatScanOnly. No match. SetupDiag:...
So I recently got an Orico drive bay combination flash card reader and USB port. The USB port works but the CF format card reader does not. I can't even tell from Device Manager if the CF or any of the other format card readers are even detected. ...
Troubleshoot Reset This PC
in Installation and Upgrade

I go into the following screen and click on Get Started. I then choose the option to Keep My Files. I am then presented with Getting Things Ready. This Won't Take Long. Which is actually true, since I almost immediately get a screen saying There...
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 06:29.
Find Us




Windows 10 Forums