Windows 10: Windows 11 failing - Setupdiag shows "SetupDiag was unable to match to any known failure...

Windows 10 22h2 device, being upgraded Setupdiag shows this - so not sure how to proceed. Any advise?SetupDiag was unable to match to any known failure signatures. SetupDiag version: 1.6.2107.27002 System Information: Machine Name = computerhome1 Manufacturer = LENOVO Model = 20QES0AL00 HostOSArchitecture = 2057 FirmwareType = UEFI BiosReleaseDate = 20230601000000.000000+000 BiosVendor = N2HET74W 1.57 BiosVersion = N2HET74W 1.57 HostOSVersion = HostOSBuildString = 19041.1.amd64fre.vb_release.191206-1406 TargetOSBuildString = 10.0.22621.1 ni_release.220506-1250 HostOSLanguag

:)

 

Upgrading to Windows 11 has failed

Unfortunately SetupDiag was unable to match to any known failure signatures.

Did you check for hardware Windows 11 compatibility at PC or motherboard support site?

 

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?

 

SetupDiag - FindAbruptDownLevelFailure

Struggeling with the same issue for month. The advice to use SetupDiag to further diagnose what causes the issue was very helpful - everything before was just guessing and trail and error.

Unfortunately my system does run into another issue (and not the same like the OP). Does anyone have an idea what can cause "FindAbruptDownLevelFailure".

@MiCrOsOfT: You should really add that information to the failure report.