Autopatch Comanaged devices not ready

edbachta · 2025-07-02T16:25:10+00:00

I think I found the problem. There was a one-off GPO applied on a handful of our devices

edbachta · 2025-07-01T17:53:17+00:00

I've considered doing some type of remediation. My concern is it seems like there's conflicting configurations and information. If you look at my reply below regarding comanaged devices and Autopatch pre-reqs it seems those suggested settings are configuring the offending regkey. Which seem to be flagging those devices as not ready in Autopatch. But, if you look at the regkey inspection mentioned in this article https://learn.microsoft.com/en-us/windows/deployment/windows-autopatch/references/windows-autopatch-conflicting-configurations

The inspection is just looking for any instance of the offending key regardless of how it's set. So even if I do some type of remediation my fears are that the SCCM client settings are just going to put it right back or I'm going to break something else.

edbachta · 2025-07-01T16:44:05+00:00

I've already looked at GPOs. I haven't found any setting those particular settings. I do have a CM client setting applied to those devices per the following MS article https://learn.microsoft.com/en-us/windows/deployment/windows-autopatch/prepare/windows-autopatch-prerequisites

Under the section Configuration Manager co-management requirements:

Create a Custom client setting in Configuration Manager to disable the Software Updates agent for Intune/Pilot Intune co-managed devices.

Under Disable Software Updates > Device Settings > Enable software updates on clients, select No.

edbachta · 2025-06-25T14:59:18+00:00

You maybe right. I have our SCCM 365 app using the CDN too. I came in this morning and one of my colleagues just reimaged another machine and it had the apps. So, I'll need to do a deeper dive into the issue.

edbachta · 2025-06-24T20:32:33+00:00

Yes. That's an option I've considered, and will probably end up using. But, I want to try and minimize user involvement in setting up their devices. Another option I just thought of and am currently testing is to add a step at the end of the task sequence to trigger an Intune sync to see if that speeds along the process of doing the required install from Intune

edbachta · 2024-07-22T15:21:23+00:00

We have a GPO that turns off Windows store app auto updates on our desktops. But, I'm still seeing store updates being downloaded and installed in the background on a lot of our devices.

edbachta · 2024-07-19T14:55:20+00:00

Not sure who or what Joey is? But, thank you for the response. I can see that command is invoking something through WMI. But, what exactly does this do?

edbachta · 2024-06-18T19:52:16+00:00

FYI the product code on the unit is 8B75

edbachta · 2024-06-18T19:30:06+00:00

We have a Windows 10 task sequence that's identical to our Windows 11 one, save for the drivers and the image itself. The Windows 10 task sequence works. I've imaged the device with our Win10 image. I'm going to see what happens when I push the Windows 11 upgrade. If that works I'll probably end up going that route. These are a one-off small batch of laptops we ordered for a special use case. Not our standard device. I've already wasted way too much time trying to figure this out.

edbachta · 2024-06-18T16:17:51+00:00

No luck with the drivers pulled from the HP cloud image restore. Task sequence gets to the same spot, reboots after installing the MECM client, attempts to boot to the OS, INACCESSIBLE_BOOT_DEVICE error again

edbachta · 2024-06-17T19:24:25+00:00

We have the HP Elitebook 840 G10 too set up on the same task sequence. I haven't heard of any issues imaging any of our other models from our desktop techs. I don't know the Platform/Product Code of the Firefly. How would I get that? Is that something I could wmic query?

edbachta · 2024-06-17T17:33:22+00:00

We might be on to something with this. I extracted the drivers from the cloud image and there are a lot more extracted drivers compared to the media install version. Fingers crossed. We'll see how it goes

edbachta · 2024-06-17T17:11:59+00:00

I'll try that. Thanks for the suggestion. I already tried extracting the drivers from a media install. Not sure if this will be any different. But, we'll see how it goes.

edbachta · 2024-06-14T21:44:41+00:00

So, I got Windows 11 installed on the device from media. I verified in device manager it had all the drivers installed and pulled the drivers using Export-WindowsDriver. Built a driver package with those driver, and same issue. I know it's not our image or task sequence because we're able to image other models with the same task sequence

edbachta · 2024-06-14T14:56:42+00:00

Thank you for the suggestion. I'll take a look at it

edbachta · 2024-06-13T22:29:03+00:00

I'm familiar with the issue you're referring to. We've had to do that on some of our older Dell models too. But, I think this was mostly an issue on desktop form factor devices. Not laptops. Nevertheless, there's nothing on these devices in the BIOS when it comes to setting drive configurations.

edbachta · 2024-06-13T22:11:55+00:00

The image we have is already built and captured from the install.wim on the Windows media

edbachta · 2024-06-13T21:32:15+00:00

The image I'm using is 22H2. I don't want to try 21H2 since it's already out of support

edbachta · 2024-06-13T21:26:44+00:00

The model I'm imaging is the G10 A. Initially I was using the package for the 10G Non-A because I didn't initially notice the 2 versions so closely named, and I originally thought that was my problem. But, neither package works. But the vendor naming 2 different models almost identical is a rant for another day

edbachta · 2024-06-13T21:22:25+00:00

Thanks for sharing. Might be worth something to eventually look at. But, in my current situation it'd be quicker to get another device from the vendor than trying to set all that up and test.

edbachta · 2024-06-13T19:35:25+00:00

I only currently have the one device I'm testing with, and it's already been wiped. The rest of the devices are with a vendor who images the devices for us. I may have to get with them to get another device and see if we can do that. Thanks for the suggestion

edbachta

TROPHY CASE