SetupDiag information next release of Windows 10

%3CLINGO-SUB%20id%3D%22lingo-sub-1361440%22%20slang%3D%22en-US%22%3ESetupDiag%20information%20next%20release%20of%20Windows%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1361440%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20the%20auto%20generation%20of%20setupdiag%20results%2C%20when%20upgrade%20failures%20happen%2C%26nbsp%3B%20still%20scheduled%20for%20the%20next%20release%20of%20Windows%2010%20like%20it%20was%20talked%20about%20at%20Ignite%20and%20if%20yes%2C%20will%20we%20be%20able%20to%20leverage%20it%20in%20ConfigMgr%20from%20the%20get%20go%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThks%20in%20advance.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1361440%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ediagnostic%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1364071%22%20slang%3D%22en-US%22%3ERe%3A%20SetupDiag%20information%20next%20release%20of%20Windows%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1364071%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F99115%22%20target%3D%22_blank%22%3E%40Stephane%20Lalancette%3C%2FA%3E%26nbsp%3BYes.%20This%20integration%20is%20available%20in%20the%20May%202020%20update%20as%20announced%20at%20Ignite.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1364122%22%20slang%3D%22en-US%22%3ERE%3A%20SetupDiag%20information%20next%20release%20of%20Windows%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1364122%22%20slang%3D%22en-US%22%3EIs%20there%20any%20additional%20documentation%20on%20how%20it%20will%20work%3F%20Will%20we%20be%20able%20to%20control%20the%20options%20in%20the%20setup%20command%20line%3F%20Like%2C%20can%20I%20force%20it%20to%20run%20setupdiag%20on%20ALL%20upgrades%2C%20even%20successful%2C%20can%20I%20redirect%20the%20output%20logs%20to%20a%20specific%20folder%3F%20Are%20there%20any%20new%20options%20like%20redirecting%20the%20registry%20keys%20to%20a%20different%20location%20as%20well%3F%20Did%20you%20work%20with%20the%20CM%20Team%20to%20have%20these%20Key%20automatically%20inventoried%3F%20Would%20really%20like%20that%20if%20these%20were%20automatically%20inventoried%20then%20a%20new%20report%20%2F%20dashboard%20in%20CM%20to%20surface%20the%20data%20easily.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1364326%22%20slang%3D%22en-US%22%3ERE%3A%20SetupDiag%20information%20next%20release%20of%20Windows%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1364326%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F350114%22%20target%3D%22_blank%22%3E%40gwblok%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhen%20setup%20launches%20setupdiag%2C%20the%20parameters%20are%3A%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%2FZipLogs%3AFalse%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%2FFormat%3Axml%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%2FOutput%3A%25windir%25%5Clogs%5CSetupDiag%5CSetupDiagResults.xml%3C%2FSPAN%3E%3CBR%20%2F%3E%3CSPAN%3E%2FRegPath%3AHKEY_LOCAL_MACHINE%5CSYSTEM%5CSetup%5CSetupDiag%5CResults%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EThese%20are%20documented%20at%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fmanufacture%2Fdesktop%2Fdeployment-troubleshooting-and-log-files%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fmanufacture%2Fdesktop%2Fdeployment-troubleshooting-and-log-files%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EWe're%20working%20with%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F63132%22%20target%3D%22_blank%22%3E%40Dune%20Desormeaux%3C%2FA%3E%26nbsp%3Bto%20get%20ConfigMgr%20integration%2C%20it%20is%20on%20their%20roadmap%2C%20but%20I'm%20not%20aware%20of%20a%20release%20date.%20Dune%20may%20have%20more.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3ERegarding%20setup%20parameters%2C%20no%20new%20parameters%2C%20but%20glad%20to%20discuss%20more%20your%20ideas%20(as%20well%20as%20ConfigMgr%20plans).%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1364367%22%20slang%3D%22en-US%22%3ERE%3A%20SetupDiag%20information%20next%20release%20of%20Windows%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1364367%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F70872%22%20target%3D%22_blank%22%3E%40Steve%20DiAcetis%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3EThanks%20Steve%3C%2FP%3E%3CP%3EWe%20currently%20run%20SetupDiag%20on%20each%20upgrade.%26nbsp%3B%20We%20grab%20the%20setup%20time%20for%20reporting%20metrics%20on%20how%20long%20it%20takes%20for%20the%20upgrade%20to%20run.%3CBR%20%2F%3EIf%20upgrade%20fails%2C%20we%20then%20inventory%20some%20of%20the%20keys%20which%20are%20populated%20into%20custom%20reports%20I've%20written%20for%20our%20upgrade%20process.%26nbsp%3B%3CBR%20%2F%3EBased%20on%20some%20of%20the%20SetupDiag%20output%2C%20we%20also%20flag%20some%20machines%20for%20reimage%20as%20we've%20learned%20some%20SetupDiag%20return%20codes%20point%20to%20issues%20that%20aren't%20worth%20resolving%20(or%20able%20to%20resolve)%20and%20the%20best%20course%20is%20Wipe%20%2F%20Load.%3CBR%20%2F%3EVery%20excited%20for%20SetupDiag%20to%20be%20integrated.%3CBR%20%2F%3E%3CBR%20%2F%3EQuestion%2C%20if%20SetupDiag%20is%20integrated%20into%20the%20upgrade%2C%20will%20we%20still%20be%20able%20to%20call%20it%20standalone%3F%26nbsp%3B%20Where%20will%20the%20upgrade%20process%20place%20it%3F%26nbsp%3B%20During%20upgrade%20does%20it%20get%20copied%20into%20a%20specific%20folder%3F%26nbsp%3B%20Does%20it%20get%20autoatmically%20%22cleaned%20up%22%20after%20upgrade%2C%20(windows.old%20folder%3F)%2C%20or%20will%20it%20stick%20around%20forever%3F%20Panther%20folder%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1384444%22%20slang%3D%22en-US%22%3ERE%3A%20SetupDiag%20information%20next%20release%20of%20Windows%2010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1384444%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F350114%22%20target%3D%22_blank%22%3E%40gwblok%3C%2FA%3E%26nbsp%3BSetup%20extracts%20all%20its%20sources%20files%20to%20%25SystemDrive%25%5C%24Windows.~bt%5CSources%2C%20including%20setupdiag.exe.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20upgrade%20is%20successful%2C%20this%20directory%20is%20moved%20to%26nbsp%3BWindows.old%5C%24WINDOWS.~BT%5CSources%20and%20the%20setupdiag.exe%20binary%20remains%20there%20unless%20deleted.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Is the auto generation of setupdiag results, when upgrade failures happen,  still scheduled for the next release of Windows 10 like it was talked about at Ignite and if yes, will we be able to leverage it in ConfigMgr from the get go?

 

Thks in advance.

5 Replies
Highlighted

@Stephane Lalancette Yes. This integration is available in the May 2020 update as announced at Ignite. 

Highlighted
Is there any additional documentation on how it will work? Will we be able to control the options in the setup command line? Like, can I force it to run setupdiag on ALL upgrades, even successful, can I redirect the output logs to a specific folder? Are there any new options like redirecting the registry keys to a different location as well? Did you work with the CM Team to have these Key automatically inventoried? Would really like that if these were automatically inventoried then a new report / dashboard in CM to surface the data easily.
Highlighted

@gwblok 

 

When setup launches setupdiag, the parameters are:

/ZipLogs:False
/Format:xml
/Output:%windir%\logs\SetupDiag\SetupDiagResults.xml
/RegPath:HKEY_LOCAL_MACHINE\SYSTEM\Setup\SetupDiag\Results

 

These are documented at:

https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/deployment-troubleshooting-and...

 

We're working with @Dune Desormeaux to get ConfigMgr integration, it is on their roadmap, but I'm not aware of a release date. Dune may have more. 

 

Regarding setup parameters, no new parameters, but glad to discuss more your ideas (as well as ConfigMgr plans). 

 

 

Highlighted

@Steve DiAcetis 
Thanks Steve

We currently run SetupDiag on each upgrade.  We grab the setup time for reporting metrics on how long it takes for the upgrade to run.
If upgrade fails, we then inventory some of the keys which are populated into custom reports I've written for our upgrade process. 
Based on some of the SetupDiag output, we also flag some machines for reimage as we've learned some SetupDiag return codes point to issues that aren't worth resolving (or able to resolve) and the best course is Wipe / Load.
Very excited for SetupDiag to be integrated.

Question, if SetupDiag is integrated into the upgrade, will we still be able to call it standalone?  Where will the upgrade process place it?  During upgrade does it get copied into a specific folder?  Does it get autoatmically "cleaned up" after upgrade, (windows.old folder?), or will it stick around forever? Panther folder?

Highlighted

@gwblok Setup extracts all its sources files to %SystemDrive%\$Windows.~bt\Sources, including setupdiag.exe.

 

If upgrade is successful, this directory is moved to Windows.old\$WINDOWS.~BT\Sources and the setupdiag.exe binary remains there unless deleted.