Skip to main content
14 events
when toggle format what by license comment
Mar 14, 2021 at 22:10 comment added Vomit IT - Chunky Mess Style @jwitt I just cleaned up old comments so consider doing the same since we got it cleaned up between our answers. I appreciate the 50 bounty and gave you +1 on both Q&A long ago. Feel free to give me an upvote if you think my efforts to help you were worth an extra +1. Thanks for the question sir!
Feb 28, 2021 at 3:05 history edited Vomit IT - Chunky Mess Style CC BY-SA 4.0
Added important detail from my comments to retain the content and detail.
Feb 21, 2021 at 4:43 history bounty ended jwitt98
Feb 21, 2021 at 4:42 comment added jwitt98 Finally, I have had success! Thank you very much for all the suggestions! I will award you the bounty since some of your suggestions led me to the eventual solution.
Feb 21, 2021 at 0:13 comment added jwitt98 After running these new commands, I am unable to update to 1903. I get a message about the upgrade path being unsupported.
Feb 19, 2021 at 23:11 comment added jwitt98 Unfortunately, the intermediate update is causing a new problem where I can't even start sysprep. It complains that package InputApp_1000.18362.387.0_neutral_neutral_cw5n1h2txyewy was installed for a user, but not provisioned for all users. When I try to remove it, it errors out saying the package cannot be removed because it is part of Windows. I have tried various things, but no luck. I'm really angry at Microsoft right now.
Feb 17, 2021 at 23:07 comment added jwitt98 It just so happens I do have a 1903 ISO and that was going to be my next step... try 1903 as an intermediate update
Feb 17, 2021 at 3:53 comment added jwitt98 So here's what I did.. I found another PC with totally different hardware, a Dell Optiplex 7440 AIO. I applied the 1703 base image. Then updated to 20H2. Removed the Appx packages that would otherwise prevent running sysprep from the start. Ran sysyprep, and on first boot, got the exact same message and same errors logged. This must either have to do with the general updating from 1703 to 20H2 or there is something on the base 1703 image causing the issue that I can't nail down. Unfortunately I don't have a clean Win 10 1703 ISO available to try to narrow it down further.
Feb 16, 2021 at 14:08 comment added jwitt98 Yes, that's correct.. all these step were done after the 20H2 update. No problems running 20H2 after updating from 1703. In-fact we have done this same update from 1703 to 20H2 to 200 other identical machines in the field and none of them have had any issues. At this point I would have probably recreated a new image from scratch, but that's not an option in this case.
Feb 16, 2021 at 4:09 comment added jwitt98 Another thing to note is that I can do a clean install of 20H2 on this machine and sysprep it without any issues. I can sysprep the 1703 image on this machine without any issues. The issue only occurs upon the first boot after updating 1703 to 20H2 and running sysprep
Feb 16, 2021 at 4:09 comment added jwitt98 I've had updating the BIOS in the back of my mind, so I went ahead and did that and reset to factory default, but still no luck. There are no options in this machine's BIOS to to switch between AHCI and IDE. Per HP documentation it can only be done via the HP replicated setup linux based utility. I can see in device manager that is is currently set to AHCI.
Feb 15, 2021 at 21:29 comment added jwitt98 I appreciate the suggestions to try. I tried all of these steps, but unfortunately the issue still persists.
Feb 15, 2021 at 2:40 history edited Vomit IT - Chunky Mess Style CC BY-SA 4.0
added 63 characters in body
Feb 15, 2021 at 2:35 history answered Vomit IT - Chunky Mess Style CC BY-SA 4.0