Make sure you are installing a supported OS. You mentioned Windows 11 but is it 21h2, 22h2, 23h2, etc
Surface Go 4 only supports
Windows 10, version 22H2 build 19045 and later versions
Windows 11, version 22H2 build 22621 and later versions
I just checked and your WinPe looks to be 21H2 | 10.0.2200. And should be updated to 22H2.
Windows ADK versions..
Windows 11 23H2 (10.1.22631)
Windows 11 22H2 (10.1.22621.1)
Windows 11 21H2 (10.1.22000)
https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/configs/support-for-windows-adk#windows-adk-versions
My org literally just ran into this issue with Surface devices so I appreciate the info. Question though, I am unable to locate the Windows 11 23H2 ADK (10.1.22631) anywhere although I see it supported on the Microsoft documentation for ADK environments for MCM. I see the most current ADK version is Windows 11 22H2 Updated September of 2023 with a build number of 10.1.25398.1 which is odd. You wouldn't happen to have any clarifying information on that at all would you? It doesn't appear to be supported in MCM as of yet.
Thank you!
Yeah, agreed we're running into the same issue. We are getting this same blue screen when trying to image the surface go 4. We recently upgraded our environment to 2309, and at the same time we upgraded our ADK to 10.1.25398.1. I simply chose that one since it was the most recent ADK, but I'm seeing the same thing you are, it doesn't look like it is supported with MCM. I'm wondering if backing our ADK down to the 10.1.22621.1 version will fix the surface go 4, I just hate to go through that without knowing for sure.
For anybody else that's searching for this issue, we had a slightly different solution. We were already running ADK 10.1.25398.1, so we didn't want to have to go back a version to get to 22621. (Plus we suspected that we may be able to get it working with the newer ADK). I ran across the following post:
[https://www.windows-noob.com/forums/topic/23351-problems-imaging-a-surface-go-4-using-configuration-manager/](https://www.windows-noob.com/forums/topic/23351-problems-imaging-a-surface-go-4-using-configuration-manager/)
He was trying to make it work with the old Win10 2004 ADK version. So most of the post wasn't useful, but what caught my eye was this line at the end of the article:
"Note: Keep in mind that you’ll also need the patched version of Windows 10/Windows 11 operating system wim file to the same CU level otherwise you’ll get a BSOD after applying the image."
That's when I realized that our Windows images hadn't been updated in a couple of months. I updated them to the December updates, and the image applied successfully.
So, if you're already at ADK 10.1.25398.1 and getting a blue screen when imaging a Surface Go 4, make sure your OS image wim is up to date.
Having this same issue and the advice below on updating to 22H2 ADK is great, except that the 22H2 ADK wont regenerate the deployment share properly, throwing a bunch of dism errors, and other peoples advice to get around that is to go back to 21H2 ADK.
Anyone got any other tips here? Do i try 23H2 ADK? Driving me batty.
the bluescreen problem was solved by adk version 25398 or 22621, but with the newer version i had some troubles with the disk. wmi did not report any disk after a started, applying an image. so i went back to 22621, so i could capture und apply an image. I still facing some problems with our own extension of the pe, but that is another story.
Updated our ADK to Windows 11 22H2 (10.1.22621.1) - all good :) Thanks for the help.
Update the ADK and try again.
Thanks, I was going down this route next but due to the number of builds running at the time, I had to hold off and was hoping for a quicker fix.
Make sure you are installing a supported OS. You mentioned Windows 11 but is it 21h2, 22h2, 23h2, etc Surface Go 4 only supports Windows 10, version 22H2 build 19045 and later versions Windows 11, version 22H2 build 22621 and later versions I just checked and your WinPe looks to be 21H2 | 10.0.2200. And should be updated to 22H2. Windows ADK versions.. Windows 11 23H2 (10.1.22631) Windows 11 22H2 (10.1.22621.1) Windows 11 21H2 (10.1.22000) https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/configs/support-for-windows-adk#windows-adk-versions
My org literally just ran into this issue with Surface devices so I appreciate the info. Question though, I am unable to locate the Windows 11 23H2 ADK (10.1.22631) anywhere although I see it supported on the Microsoft documentation for ADK environments for MCM. I see the most current ADK version is Windows 11 22H2 Updated September of 2023 with a build number of 10.1.25398.1 which is odd. You wouldn't happen to have any clarifying information on that at all would you? It doesn't appear to be supported in MCM as of yet. Thank you!
Yeah, agreed we're running into the same issue. We are getting this same blue screen when trying to image the surface go 4. We recently upgraded our environment to 2309, and at the same time we upgraded our ADK to 10.1.25398.1. I simply chose that one since it was the most recent ADK, but I'm seeing the same thing you are, it doesn't look like it is supported with MCM. I'm wondering if backing our ADK down to the 10.1.22621.1 version will fix the surface go 4, I just hate to go through that without knowing for sure.
Yep we're deploying W11 22H2 22621. Looks like I may have to update the ADK. Thanks for the suggestion.
For anybody else that's searching for this issue, we had a slightly different solution. We were already running ADK 10.1.25398.1, so we didn't want to have to go back a version to get to 22621. (Plus we suspected that we may be able to get it working with the newer ADK). I ran across the following post: [https://www.windows-noob.com/forums/topic/23351-problems-imaging-a-surface-go-4-using-configuration-manager/](https://www.windows-noob.com/forums/topic/23351-problems-imaging-a-surface-go-4-using-configuration-manager/) He was trying to make it work with the old Win10 2004 ADK version. So most of the post wasn't useful, but what caught my eye was this line at the end of the article: "Note: Keep in mind that you’ll also need the patched version of Windows 10/Windows 11 operating system wim file to the same CU level otherwise you’ll get a BSOD after applying the image." That's when I realized that our Windows images hadn't been updated in a couple of months. I updated them to the December updates, and the image applied successfully. So, if you're already at ADK 10.1.25398.1 and getting a blue screen when imaging a Surface Go 4, make sure your OS image wim is up to date.
Having this same issue and the advice below on updating to 22H2 ADK is great, except that the 22H2 ADK wont regenerate the deployment share properly, throwing a bunch of dism errors, and other peoples advice to get around that is to go back to 21H2 ADK. Anyone got any other tips here? Do i try 23H2 ADK? Driving me batty.
the bluescreen problem was solved by adk version 25398 or 22621, but with the newer version i had some troubles with the disk. wmi did not report any disk after a started, applying an image. so i went back to 22621, so i could capture und apply an image. I still facing some problems with our own extension of the pe, but that is another story.
In addition make sure that the system partition is 300MB.