Windows Capability Fails

[BenColeAu]

AutopilotBranding.log

Hey @mtniehaus,

Just given this my first go and would love some pointers on what I am doing wrong here, I suspect it's something silly.

Attached is my log file and a few points here are failing.

1. Features fail to install - source fails to find the feature for 3.5 & WMIC
2. Fails to Remove Microsoft.DesktopAppInstaller (Not sure if this is actually present on windows 11) - I'll remove this from the config and test.
3. Potentially my Languages are failing I suspect due to the difference in file name in my CAB files. - I'll also attempt updating this and testing agin.
4. This doesn't appear to update the Locale of the device - defaults to United Kingdom. - Let me know if this is the case.

Thanks,
Ben

[BenColeAu]

Just confirmed I have configured the locale as en-AU in the language.xml, this might be overridden by the OOBE window the user is currently only presented with 2 options being United states and United kingdom so might just be the base image on the device. I can manually update this in the settings post install.

[BenColeAu]

Completed the changes above appear to have fixed all issues except for Locale this appears to be controlled at the first OOBE screen.

The other issue is the detection of the Tag file still continues to fail with the following error
EnforcementErrorCode: -2016214839.
The Intune portal tells a different story
The device install status fails with the following

However the User install status reports this as installed without issue.

[BenColeAu]

Addressing the detection issue I've ended up moving it all to a C:\Temp directory including the .ps1.tag file and logs.
This passes both detection post login to the desktop but still fails in autopilot with the same error on timeout.

@mtniehaus

I'm going to try adapting an exit with code at the end of the script

[shwetanksandhu]

Hi @BenColeAu

Apparently, I am also experciening exact same issues:

1. The Autopilot Branding app gets stuck at the ESP and upon checking the logs using Shift + F10, the logs sort of gets stuck at Adding Feature - Were you able to find a workaround to this?
2. The application fails to detect with the same error as you mentioned above in the Intune portal "The unmonitored process is in progress, however, it may timeout. (0x87D300C9)".

Any help with this will be greatly appreciated.

Best
Shwetank

[BenColeAu]

Hi @BenColeAu

Apparently, I am also experciening exact same issues:

1. The Autopilot Branding app gets stuck at the ESP and upon checking the logs using Shift + F10, the logs sort of gets stuck at Adding Feature - Were you able to find a workaround to this?
2. The application fails to detect with the same error as you mentioned above in the Intune portal "The unmonitored process is in progress, however, it may timeout. (0x87D300C9)".

Any help with this will be greatly appreciated.

Best Shwetank

I recommend writing out a tag file or reg key to help with detection and remove the features and install those with a pshell script post oobe autopilot.
Hope this helps, I ended up not using this script and went with different methods.
Thanks,
Ben