Sysprep_succeeded.tag does not already exist, no need to delete anything

Question

Sysprep_succeeded.tag does not already exist, no need to delete anything

~OSD~ 2,201

SYSPRP FCreateTagFile:Tag file C:\Windows\system32\sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything What is supposed to be "deleted" by Sysprep if it could have found the file:

C:\Windows\system32\sysprep\Sysprep_succeeded.tag

Accepted answer

0 additional answers

Your answer

Answer 1

AlexZhu-MSFT 6,591 Moderator

Hi,

If it fails during Sysprep, we can check the log file for trouble shooting. For example, Microsoft Store sometimes may prevent the Sysprep process.

When it succeeds and generates the tag, it will do the following:

All unique system information is removed from the Windows installation. The security ID (SID) resets, any system restore points are cleared, and event logs are deleted.

The next time the computer starts, the specialize configuration pass runs. A new security ID (SID) is created, and the clock for Windows activation resets, if the clock has not already been reset three times.

Regards,

Alex

~OSD~ 2,201 Reputation points

2024-01-24T08:28:36.86+00:00

@AlexZhu-MSFT Thanks. So in other words, if Sysprep_succeeded.tag is NOT present, Sysprep will NOT generate the new SID and activation reset?
AlexZhu-MSFT 6,591 Reputation points Moderator

2024-01-25T07:55:26.1433333+00:00

Hi,

Thank you for the response. The message above is just a warning, not error messages. As far as I know, the logic is as below:

1, When sysprep first runs, it will reset sid, clear restore points and delete event logs, after all the stuff is done, it creates the file to indicates an entire process is completed, which prevents abnormal shutdown during the process.

2, When the template computer restarts, it will create a new sid. When we run sysprep for the second time, it will firstly check if the file exists. If yes, remove the file, otherwise, print the above message and continue with the sysprep process.

Regards,

Alex
~OSD~ 2,201 Reputation points

2024-01-25T08:37:23.6166667+00:00

Ok, so the conclusion is if .tag is available or not, Sysprep with generalize will always reset the SID and activation clock ... correct?
AlexZhu-MSFT 6,591 Reputation points Moderator

2024-01-26T01:08:21.17+00:00

Correct. The file is just to make sure then entire process is intact.
~OSD~ 2,201 Reputation points

2024-01-26T12:32:52.0533333+00:00

Perfect, thanks for the confirmation Alex.

Share via

Sysprep_succeeded.tag does not already exist, no need to delete anything

0 additional answers

Your answer