Issues with Sysprep on Windows 10 Pro 22H2 in Azure VM

0
3
Asked By CloudySky23 On

I'm trying to create a generalized image of Windows 10 Pro 22H2 from within an Azure Virtual Machine, but I'm running into some issues with Sysprep failing. The error message indicates that the Microsoft.BingSearch package was installed for a user but not provisioned for all users, which is leading to the failure. I've attempted to remove the BingSearch package using PowerShell commands and verified that there are no deprovisioned app entries in the registry. The only user on the system is the local admin, and I've also rebooted to no avail. I need to keep Microsoft Store and Xbox apps available, so downgrading to Server 2022 isn't a viable option for me. Has anyone else experienced this issue with Sysprep in Azure VMs? Is Windows 10 Pro 22H2 really broken for Sysprep in this context? Would switching to LTSC 2021 or 2024 resolve this without causing licensing issues? I really appreciate any insights, as I've been stuck on this for days!

3 Answers

Answered By ScriptMaster007 On

You might try removing the BingSearch app entirely with PowerShell commands like these: `Get-AppxPackage -AllUsers | Where-Object {$_.Name -eq "Microsoft.BingSearch"} | Remove-AppxPackage -AllUsers` and `Remove-AppxProvisionedPackage -Online -PackageName "Microsoft.BingSearch_1.1.33.0_x64__8wekyb3d8bbwe"`. After that, make sure there are no leftover entries in AppData or the registry, then give Sysprep another go. It seems like you might not have completed all the necessary prep steps. And honestly, it's probably not the best time to be working on a Windows 10 image.

Answered By TechieGuy99 On

Have you considered using the Azure Image Builder? It's worth a shot. Also, just out of curiosity, have you tried running this on Windows 11? Since Windows 10 is nearing the end of support, building images for it might not be the best idea right now.

Answered By BingHater88 On

I totally feel your pain! I had a problem like this where I thought I'd removed everything properly but kept getting the same Sysprep failure. Just double-check your commands and ensure that you're cleaning up properly. Good luck!

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.