This would also account for why my Task Sequence failed with the box checked to “Ignore any dismissible compatibility messages” which is supposed to be the same setting as using “Compat=IgnoreWarning” in the INI. I believe the Win11 installer forces this ScanOnly to happen before it actually installs to make sure things are good to go beforehand since it’s got more stringent requirements. This caused the OEM#.inf files to be detected as blockers again. The CopyLogs path wasn’t being used and the Compat setting was “ScanOnly”. Looking at the logs again, I saw that when the device booted and ran the setup from C:$WINDOWS.~BT\Sources\Panther folder, my settings from the setupconfig.ini weren’t being used. Then the reboot happened and the install failed. Logs show that the command line had the “/compat ignorewarning” as desired. ![]() Kicked off the servicing update and it pulled those settings according to the logs which were also put into the specified temp folder. As a general rule, if someone has flair, they almost definitely know what they're talking about.Ĭreated the setupconfig.ini file with the entry for “Conpat=IgnoreWarning” and one for copying logs to a temp folder.
0 Comments
Leave a Reply. |