question

RS4KING-4083 avatar image
0 Votes"
RS4KING-4083 asked ·

Sysprep/Capture Rebooting into CMD

I have a fully updated Windows that has no applications aside from what's in the Windows 10 ISO. I tried to run my sysprep and capture and it does its thing and then restarts the computer (as it should) but it doesn't log back into Windows. Instead, it reboots into the MDT set up and automatically goes to the command prompt showing X:\windows\system32.

I've seen this before and I know that if I close the CMD window it will continue to reboot back into the same CMD prompt. It's basically stuck in this loop. I know that if I go to CMD prompt and delete the C:\MININT folder, it will allow me to boot into Windows but my sysprep doesn't finish or do anything when I log back in.

Any ideas why it boots into the CMD prompt in the first place and not into Windows to finish the sysprep/capture?

Thanks in advance!

mem-mdt
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

RS4KING-4083 avatar image
0 Votes"
RS4KING-4083 answered ·

Update: I seemed to have fixed it. I have no idea what fixed it but here is what I did:

  1. Removed my 2nd deploymentshare (I had created a whole new one when I was trying to figure out what the hell was going on)

  2. I decided to try and run the LiteTouch.vbs while logged into the user I set up during Windows First Time setup. Before, I was going into LUSRMGR.msc and re-enabling the Administrator account, then deleting the newly created account that I had set up initially and running LiteTouch using the built-in Administrator account that's disabled during setup (I honestly think it was this that fixed the issue)

  3. Removed the changes I did in the Unattend.xml file. I had made changes to the AutoLogon portion of the script and added Administrator and local password. I removed this information.

  4. Updated my username/password/domain in the CUSTOM.INI file. I was using another account that wouldn't have worked.


I hope this helps someone else. Just to note, I was also having issues with the sysprep/capture failing due to the Error AppX Package is not installed for all users etc.


·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AllenLiu-MSFT avatar image
0 Votes"
AllenLiu-MSFT answered ·

Hi, @RS4KING-4083
Thank you for posting in Microsoft Q&A forum.
Have we tried to delete the C:\MININT folder first and then run sysprep and capture?
We may check below article to see if we missed any steps:
https://theitbros.com/capture-windows-10-reference-image/
(Third-party link, just for your reference)


If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 2 ·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Yes, that's how I'm about to load back into Windows. I run the RMDIR command in the CMD prompt to delete the MININT folder, then I close the CMD prompt and it loads into Windows. However, when loading into Windows, it acts like it if it's going through its first time setup, but eventually it loads into my Windows.

0 Votes 0 ·

After I deleted the folder and loaded into Windows. I tried running the LiteTouch.vbs script again, it ran and restarted but this time it actually loaded into Windows without an issue, but nothing happened. I loaded into Windows and the sysprep/capture didn't finish or start up or anything after loading back in.

I do noticed that the following folders got created:

_SMSTaskSequence
Boot
MININT

Any ideas?

0 Votes 0 ·