Event banner
Event details
110 Comments
- We've had this issue when doing an Intune Wipe for a single device, it is successful, however when doing Intune Wipe for many devices, such as 10-20 devices, a large number of them fail. When the wipe fails, we see the computer hits 75% of resetting windows and then gives "reverting changes" message. After it reboots, will get this message when attempt to login: "The User Profile Service failed the sign-in. User profile cannot be loaded." The devices we are wiping are hybrid joined, Win10 co-managed. We are running the wipe command from https://intune.microsoft.com/#view/Microsoft_Intune_DeviceSettings/DevicesMenu/~/overview and both check-boxes are de-selected. We've gone back and forth with support since June 2023 but there hasn't been a response or answer for awhile now. I'm curious if we could talk about this more on how the "doWipe" command could result in these errors and ways to isolate where the issue is coming from or even better a solution. Thanks!
- I would bet, those PCs have an OEM injected boot-start dependent driver that is not surviving the wipe process. Most likely, a storage driver. Have you tried installing a clean (and recent) copy of Windows Pro on them? If the installation requires a storage driver, that is your problem.
- Interesting. We'll take a look at drivers but like I mentioned, the wipe fails midway. And to add to that we also saw it deletes the users ntuser.dat file which gives us that error message. We've seen this on Lenovo P1's and X1's.
- Does Microsoft have any plans to integrate Windows Updates (with Driver Updates) into Autopilot?
Though I would prefer systems that can start from a clean copy of Windows, then Plug and Play apply the better driver from Windows Update once the system is running, OEMs are allowed to inject any boot-start required drivers. As long as those OEM injected boot-start drivers survive a wipe, it should be fine. Just reset and go. That is... until a clean copy of Windows ever needs to be installed.
To help find vendors and products that have made the transition to modern device management, there is a community-maintained spreadsheet named "Modern Windows Management Database".
https://1drv.ms/x/s!AgG_boPR-xfWjN9i2Z_y_8ErM6t--A
Please help by contributing your experiences to it.
Thanks for participating in today's Windows. Cloud. Management. Your questions answered! For reference, the panel covered this topic at around 05:30.
- There are times when a system is missing important drivers such as the Wi-Fi network driver. If the system is being autopiloted from a USB Ethernet wired connection the user must wait for Windows Updates to complete before the Wi-Fi drivers are installed. Maybe an option in the ESP to install only driver updates would be helpful. Another option might be to place a "windows update" button on the autopilot login screen so the system can be updated before Autopilot is started. As for the having the user to wait for it to complete it think if some sort of status bar that showed the percent complete the user would be OK waiting. Without a status update the user may think autopilot is stuck and either power cycle the machine or call the help desk.
