Applying Sysprep to a Windows installation (preparing for use). How to run SysPrep after upgrading Windows Windows 10 sysprep does not work

I encountered a strange error when trying to execute SysPrep on an already installed system that was planned to be used to create a reference image for deploying Windows 10 using System Center Configuration Manager 2012 R2. When running SysPrep, an unexpected error appears:

Sysprep was unable to verify the Windows installation. For more information, see the log file %Windows%\System32\Sysprep\Panther\setupact.log. Once the problem is resolved, test the installation again using Sysprep.

In the English version of Windows 10 the error is similar:

Sysprep was not able to validate your Windows installation, Review the log file at %Windows%\System32\Sysprep\Panther\setupact.log for details. After resolving the issue, use Sysprep to validate your installation again.

Let's open and analyze the errors in the Sysprep setupact.log utility log file. The following line immediately catches your eye:

2016-08-01 10:22:51, Error SYSPRP spopk.dll:: Sysprep will not run on an upgraded OS. You can only run Sysprep on a custom (clean) install version of Windows.

Those. The error explicitly states that it is not allowed to run Sysprep on systems that were upgraded from a previous version of Windows. In our case, this is exactly the case: one system was obtained by upgrading from Windows 7 to Windows 10, the second through an upgrade from Windows 8.1. Indeed, according to knowledge base article KB828287: Microsoft does not support the use of Sysprep to create images for Windows installations that have been upgraded through upgrade mode (SP installation is not considered an upgrade). Windows only allows sysprep to be performed on systems resulting from a clean install. Is it really necessary to reinstall the system from scratch in this case?

I managed to find a simpler solution. Using Process Monitor with a filter for the sysprep.exe process and comparing clean and “updated” Windows 10, we were able to obtain a list of registry keys that are checked by Sysprep at startup to determine whether this system is clean or “updated”. So, what needs to be done to reset the “updated” system marker for Windows 10, which is checked by the Sysprep utility (everything is similar for other versions of the OS):

Important. The technique described below is not officially supported by Microsoft, and there is no guarantee that future problems will not arise with the system image obtained in this way.

Advice. In the case of Windows 10, in order for SysPrep to work, we additionally had to remove all non-standard Modern applications that were individually (not in mode) installed from the Microsoft Store by system users.

This can be done by deleting all user profiles (if applicable), completely for all users (not a recommended method), or manually deleting such applications. The last option is implemented like this:

Let's get a list of all installed Metro applications in the profiles of all users (we are only interested in packages with the Installed status): Get-AppxPackage -AllUser | Format-List -Property PackageFullName,PackageUserInformation
And sequentially removing them this way: Remove-AppxPackage -Package Or like this: Remove-AppxProvisionedPackage -Online -PackageName

This documentation has been archived and is no longer maintained.

Applying Sysprep to a Windows installation (preparing for use)

Use the remedy Sysprep to prepare the Windows installation. To deploy a Windows image to different computers, you must first prepare the image. You can use the system preparation tool (Sysprep), or you can specify an option in a response file to prepare the image as part of a silent installation. To prepare the image, you need to remove information about a specific computer from it. This process is called preparation image.

In most Windows 8 deployment scenarios, it is no longer necessary to use the SkipRearm answer file option to reset the Windows activation clock when you run the command Sysprep on the computer several times. In Windows 8, the SkipRearm parameter is used to indicate the Windows licensing state. If you specify a retail product key or a multiple install key, Windows activates automatically. Team Sysprep can be performed no more than 8 times with one Windows image. After running Sysprep 8 times on a Windows 8 image, you need to re-create the Windows image. For more information about the Windows features and settings that you can add to an answer file, see the Unattended Windows Installation Reference.

Attention

Don't use the Windows Store to update a Windows Store app before running sysprep /generalize. Sysprep cannot prepare the image in this scenario. This issue also affects Windows Store apps that come with Windows 8 (such as Mail, Maps, Bing Finance, Bing News, and others). This may occur when you configure an installation in audit mode as a built-in administrator or when a special account is used. The following error appears in the sysprep log files (%WINDIR%\System32\Sysprep\Panther):

Was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

For work Sysprep /generalize requires that all applications be provisioned for all users. However, when you update an app from the Windows Store, the app becomes unprovisioned and account bound.

Instead of using the Windows Store to update applications, you should sideload updates to line-of-business applications or encourage users to update applications on target computers using the Windows Store. In managed environments where Windows Store access is disabled by your IT administrator, you won't be able to update Windows 8 Store apps.

If your Network Policy Server (NPS) configuration contains RADIUS clients or groups of external RADIUS servers, you must remove this information before deploying it to another computer. For more information, see .

In this section

Preparing the image for use

When you prepare a Windows image, Windows Setup processes settings during the configuration phase. Even if the service computer and the reference computer have the same hardware configuration, you must run the command Sysprep with parameter /generalize. Team Sysprep /generalize removes unique system information from a Windows installation, making it safe to use the image on another computer. However, you can save the drivers during the setup phase.

Important

When you set up a reference computer, Windows Setup installs drivers for all detected devices. By default, Windows Setup removes these drivers when preparing the system for use. If the image is deployed to computers with the same hardware and devices, you will need to have Windows Setup install the same drivers again. To leave these drivers on the computer during system preparation, set the Microsoft-Windows-pnpsysprep | PersistAllDeviceInstalls value true. More information about Windows components related to Sysprep that you can add to the answer file, see Unattended Windows Installation Reference.

When executing the command Sysprep Windows replaces only the computer security identifier (SID) on the operating system volume. When Sysprep prepares the image, only the general section is prepared. Therefore, if several operating systems are installed on one computer, you must perform Sysprep for each image separately.

Preparing the image for use

Add one of the following parameters to your response file.

Use the Microsoft-Windows-Deployment | Generalize. Set Mode to OOBE or Audit, and for ForceShutdownNow the value true. The computer will automatically prepare the image for use and shut down.

Add the Microsoft-Windows-Deployment | Reseal into the setup phase. Set Mode to Audit. After the computer boots into audit mode and the window displays System Preparation Tool use one of the following methods:
- In the window System preparation program select Preparation for use and click Shutdown and then click OK.
  
  Close the window System Preparation Tool %WINDIR%\system32\sysprep. Use the command Sysprep with parameters /generalize, /shutdown And /oobe. For example:
  
  The computer will prepare the image for use and shut down.

Dism/capture-image in the Deployment Image Servicing and Management Tool ( DISM).

For more information, see and.

If you need to configure additional settings, you can enter audit mode manually and perform the configuration before you prepare the image for use and deploy it.

Optional action. Entering audit mode manually before preparing the image for use

When the startup screen appears when you turn on your computer for the first time, press CTRL+SHIFT+F3. Windows will restart your computer in Audit mode and display the System preparation program.

Attention

The Ctrl+Shift+F3 keyboard shortcut prevents you from skipping any steps in the startup process when you first turn on your computer, such as running scripts and applying response file settings during Setup.

Add all the settings you want to enable.

In the window System preparation program select Preparation for use and click Shutdown and then click OK

Close the window System Preparation Tool, open a command prompt window as administrator and go to the directory %WINDIR%\system32\sysprep. Use the command Sysprep with parameters /generalize, /shutdown And /oobe. For example:

Sysprep /generalize /shutdown /oobe

The computer will prepare the image for use and shut down.

After shutting down your computer, capture the image using image capture. For this you can use the command Dism/capture-image in the means DISM.

Deploy this image to a reference computer. When you boot your reference computer, the startup screen appears when you turn on the computer for the first time.

For more information about audit mode, see:

There is no need to say goodbye to the smooth operation of the Windows operating system, and with it the installed, configured, activated licensed programs, if there is a need to replace the computer’s motherboard. Windows itself provides a special tool for this kind of event - the Sysprep utility. Below we will consider in detail how to use it not only to resolve the issue with the operability of the operating system after replacing the motherboard, but also to completely transfer working activated Windows to another computer with different hardware components from the current ones.

We will transfer to another computer the most current version of the operating system from Microsoft - Windows 10. In addition to the built-in Sysprep utility, the free edition of the backup program AOMEI Backupper will help us in this matter. In its place there can be any other backup program; the essence of the process of transferring Windows to another computer with different hardware will not change. AOMEI Backupper was chosen because it is easy to use and free to use.

1. About the Sysprep utility

The Sysprep utility removes drivers and other system data about the hardware components of the computer, without affecting user data - installed and configured programs, files on the system drive, shortcuts on the desktop and in the Start menu. This utility was created by Microsoft to simplify the installation of Windows and software on a production scale. The installed operating system with already implemented and configured programs, upon completion of Sysprep, becomes a reference image, which is subsequently deployed on various computer devices of companies. On each of them, you subsequently need to install drivers for individual components and external devices that are not installed automatically. And, of course, you need to activate Windows separately on each computer.

The Sysprep utility can be used when replacing not only the motherboard, but also the processor. Replacing the latter is not the case in all cases, but in some cases it may lead to failures and errors in the operation of Windows. If and as soon as they are found, you can resort to Sysprep.

2. Preparatory stage

Whether it’s replacing the motherboard or processor, or transferring Windows to another computer with different hardware, before using the Sysprep utility, it’s better to create a restore point just in case. An alternative is a backup using the AOMEI Backupper program, which we will use to transfer the system to another computer. Before running the Sysprep utility, it is also advisable to disable your antivirus and firewall.

The preparatory steps listed above are sufficient if you are replacing the motherboard or processor, but to transfer Windows to another computer you will need a couple more things.

After the Sysprep utility removes the binding to the hardware components of the computer, you will need to create a backup copy of Windows. This must be done in pre-boot mode using bootable media with a backup program. To create one you will need a CD/DVD media or flash drive.

You also need to consider how to transfer your Windows backup. To do this, you will need an external HDD, a capacious flash drive, or access to a local network resource if the computers are on the same small network. When migrating an operating system from one PC build to another, you can save a backup copy on the hard drive of the first PC, and then temporarily connect that drive to the second PC. If the computers are located at a distance, and the target computer has at least some operating system, a Windows backup can be saved on the hard drive of the source computer. And then transfer it to the target computer using cloud storage. But even if the target computer does not have any operating system, but the hard drive is partitioned, you can put any files from the Internet on it if you boot from a Live disk (or from a disk with a Linux distribution in mode without installing the system).

3. AOMEI Backupper Bootable Media

We omit this paragraph of the article for cases of replacing the motherboard or processor, but in the case of transferring Windows to another computer with different hardware, we proceed to creating bootable media with a backup program. This is done very simply using the AOMEI Backupper program. Go to the last section “Utilities” and click “Create bootable media”.

Then select “Windows PE”. Click “Next”.

Select the media – CD/DVD, flash drive or ISO image. The latter must be selected if the work is carried out with a computer based on BIOS UEFI. AOMEI Backupper cannot write UEFI bootable media. But other programs can do this (for example,). Using these, using the ISO image created by AOMEI Backupper, you will need to create UEFI bootable media.

4. Reset hardware settings using the Sysprep utility

Now we proceed directly to removing the binding to the hardware components of the computer. Press the +R keys and in the “Run” command field enter:

After clicking “Ok”, the system folder with the executive file of the Sysprep utility will open in Explorer. Let's launch it.

A window with Sysprep launch settings will open. We leave the default option to go to the system welcome window (OOBE). To prevent Windows activation from failing, do not touch the checkbox for the preparation for use option. And, on the contrary, we set it when we need to reset the activation. Why an activation reset may be necessary will be discussed below, in paragraph 8 of this article. The third, also the last setting, is the way to complete the work. In the drop-down list, change the preset reboot to turn off the computer. Click "Ok".

The Sysprep utility will do its work and the computer will shut down. The next time you start Windows, it will already adapt to the new hardware. Therefore, after turning off the computer, we can proceed to replacing the motherboard or backing up Windows in pre-boot mode. If you replace the motherboard or processor, you can omit the backup items and immediately start starting the system - go to paragraph 7 of the article.

5. Backup of Windows without connection to the computer hardware

To create a backup copy of Windows, which, after running the Sysprep utility, will not be tied to the hardware of the current computer, load it from a previously created CD/DVD or flash drive with the AOMEI Backupper program. If you use an external HDD or a large flash drive to save a backup copy, connect them.

In the AOMEI Backupper window, go to the “Backup” section and select “System Backup”.

The disk with AOMEI Backupper will be defined as 500 MB reserved by the system, the system disk will be designated with the letter D. Select the latter in step 1. In step 2, indicate the path to the backup storage location - external media, non-system disk partition, network resource. Click “Launch”.

In the window that the backup process has started, we will use the option to turn off the computer upon completion of the operation.

After creating a backup copy, the computer will turn off itself, and the external, internal HDD or flash drive can be disconnected and connected to the target computer where you plan to transfer Windows.

6. Restoring Windows on a computer with different hardware

Having connected the media with the created backup file to the target computer (or downloaded the backup file from the cloud storage to its hard drive), now on this computer we set the priority for booting from a CD/DVD disk or flash drive with the AOMEI Backupper program.

In the AOMEI Backupper window, go to the “Rollback” section. Click on the “Path” column at the bottom.

We indicate the path to store the backup file, after which the program will offer to restore the system from it. Click “Yes”.

In the next window, at the top, click on the backup copy, and at the bottom, check the “Restore the system to another location” option. And click “Ok”.

In our case, the backup file arrived on the target computer along with the hard drive removed from the source computer (Disk 1). The hard drive of the target computer (Disk 0), as we see in the screenshot, is not even partitioned. But this is not necessary. Just select it and click “OK”.

With the hard drive partitioned, select only the system partition. Important: when running backup programs from bootable media, the drive partition letters may differ from those listed in the system explorer. Therefore, you need to navigate disk partitions by their size.

If the system partition captured in the backup is smaller in size than the partition where Windows will be restored, in the operation summary window of AOMEI Backupper we will find the option “Resize partition”. Let's press it.

In order for Windows to be restored from a backup to the entire volume of the system partition, and after it there is no unallocated disk space left, we pull the slider of the visual disk layout graph to the end or to the required limit. When finished, click “Ok”.

To start the Windows recovery process, in the operation summary window, click “Run”.

As when creating a backup, check the box for the option to automatically turn off the computer after the system restore operation is completed.

7. Running Windows on a computer with different hardware

When turning on the target computer, we set the boot priority from the hard drive. Either after replacing the motherboard or after transferring Windows to another computer, in either case we will see the same picture - the process of reinstalling drivers for the computer’s hardware components will begin. This will be followed by a welcome window with options for choosing a language, region, and time zone. Specify the required information and click “Next”.

If the original Windows 10 was activated, the next window will ask you to accept the license agreement.

At the same stage, if the original Windows 10 was previously without activation, you will be prompted to enter. This can be done later in the system itself if you click the “Do later” option.

In the system settings window, in our case, select standard.

Next, as with a normal installation of Windows 10, the process of creating an account will follow. No need to worry about your existing account with its settings and data. She's fine and we'll have access to her later. The new account will be temporary and can be deleted later. Select “This computer belongs to me” and click “Next”.

Skip the prompt to create a Microsoft account.

And create a local (that same temporary) account. Enter the name, leave the password fields empty and click “Next”.

This will be followed by the final stage of Windows 10 settings.

Finally, we will find ourselves inside the new, just created account. We exit from it: press the +X keys and select exit from the system.

Let's go to the lock screen and see the old account. Let's go into it.

And we proceed to check if everything is in order with the data. Start menu settings, desktop shortcuts, installed programs, files on drive C - all this should remain untouched.

Now all that remains is to delete the temporary account if it is not needed. Go to the “Settings” application, open the “Accounts” section, and in it – “Family and other users”. We delete an unnecessary account.

8. Nuances of activation and launching the original Windows

Since one product key can activate only one Windows, there is a possibility that activation will fail in a system transferred to another computer. And this will happen soon after the source system has access to the Internet. Microsoft allows you to transfer an activated operating system to another computer, but on the condition that it is removed from the first computer. However, if, for example, a computer with original Windows is passed on to another family member, it is not necessary to say goodbye to this system. It can simply remain temporarily without activation until money appears in the family budget to purchase a new activation key. What needs to be done for this?

As mentioned, activating the Prepare for Use setting may cause Sysprep to reset Windows activation. Activation reset is limited to only three times. This feature in earlier versions of Windows was abused by many to extend the 30-day trial period of using the licensed system. In our case, the transfer of Windows was conceived together with its activation, and above, when running the Sysprep utility in its settings, we limited ourselves to only deleting the binding of the computer to a specific hardware. To prevent activation of Windows transferred to another computer from failing, you must turn off the Internet before turning on the original Windows computer. Then, after the same steps as described in the previous paragraph, in the original Windows you need to re-run the Sysprep utility, but with the activation reset settings - i.e., by checking the “Preparing for use” option.

That's all.

Have a great day!

Hello everyone, today I will tell you how to solve the error Sysprep could not verify the installation of Windows in Windows 10. Let me remind you that Sysprep is a procedure for preparing a reference image, to anonymize it, all unique identifiers (SID, GUID, etc.) will be removed from the system. When else it may be necessary, for example, if you create your own Windows 10 build.

For example, OEM manufacturers use sysprep so that you receive, for example, a laptop in a preconfigured state, and all you have to do is create an account and log in.

This is what the error Sysprep could not verify the Windows installation looks like more clearly; it occurs to me when I enter the audit mode phase to clear all accounts.

And so, after surfing the Melkosoft forums, I really didn’t find a clear answer, of course syspread sends you to the setupact.log file, and there you can smoke for a long time what’s the matter, but everything turned out to be very simple. Do not check the Preparation for use checkbox during the transition to system audit mode and everything will work as it should.

If you get this error at the OOBE stage, then with a high degree of probability everything in the log will have an error similar to this one

Package 9E2F88E3.Twitter_4.3.3.0_x86__wgeqdkkx372wm was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image

Its meaning is that there is an account that has packages that are not presented for all users, and I advise you to delete these extra accounts, and leave only the Administrator; if there is a need to leave them, then delete the packages associated with it.

Sysprep will not run on an upgraded OS. You can only run Sysprep on a custom (clean) install version of Windows

As I wrote above, the version updated from the previous series will not work with sysprep.

pyatilistnik.org

How to run SysPrep after upgrading Windows

08/02/2016 Windows 10, Windows 8

I encountered a strange error when trying to run SysPrep on an already installed system that was planned to be used to create a reference image for deploying Windows 10 using System Center Configuration Manager 2012 R2. When running SysPrep, an unexpected error appears:

In the English version of Windows 10 the error is similar:

Let's open and analyze the errors in the Sysprep setupact.log utility log file. The following line immediately catches your eye:

2016-08-01 10:22:51, Error SYSPRP spopk.dll:: Sysprep will not run on an upgraded OS. You can only run Sysprep on a custom (clean) install version of Windows.

Those. The error explicitly states that it is not allowed to run Sysprep on systems that were upgraded from a previous version of Windows. In our case, this is exactly the case: one system was obtained by upgrading from Windows 7 to Windows 10, the second through an upgrade from Windows 8.1. Indeed, according to knowledge base article KB828287: Microsoft does not support the use of Sysprep to create images for Windows installations that have been updated through upgrade mode (installing the SP is not considered an upgrade). Windows only allows sysprep to be performed on systems resulting from a clean install. Is it really necessary to reinstall the system from scratch in this case?

Important. The technique described below is not officially supported by Microsoft, and there is no guarantee that future problems will not arise with the system image obtained in this way.

Advice. In the case of Windows 10, in order for SysPrep to work, we additionally had to remove all non-standard Modern applications that were individually (not in provision mode) installed from the Microsoft Store by system users.

This can be done by deleting all user profiles (if applicable), completely deleting all Metro applications for all users (not a recommended method), or manually deleting such applications. The last option is implemented like this:

Let's get a list of all installed Metro applications in the profiles of all users (we are only interested in packages with the Installed status): Get-AppxPackage -AllUser | Format-List -Property PackageFullName,PackageUserInformation
And sequentially removing them this way: Remove-AppxPackage -Package . Or like this: Remove-AppxProvisionedPackage -Online -PackageName

More posts on the topic: Windows 10, Windows 8 Did you like the article? Say thank you and tell your friends!

winitpro.ru

Applying Sysprep to a Windows installation (preparing for use)

Use the Sysprep tool to prepare your Windows installation. To deploy a Windows image to different computers, you must first prepare the image. You can use the system preparation tool (Sysprep), or you can specify an option in a response file to prepare the image as part of a silent installation. To prepare the image, you need to remove information about a specific computer from it. This process is called image preparation.

In most Windows 8 deployment scenarios, it is no longer necessary to use the SkipRearm answer file option to reset the Windows activation clock when you run the Sysprep command on a computer multiple times. In Windows 8, the SkipRearm parameter is used to indicate the Windows licensing state. If you specify a retail product key or a multiple install key, Windows activates automatically. The Sysprep command can be run up to 8 times on a single Windows image. After running Sysprep 8 times on a Windows 8 image, you need to re-create the Windows image. For more information about the Windows features and settings that you can add to the answer file, see the Unattended Windows Installation Reference.

Attention

Do not use the Windows Store to update a Windows Store application before running sysprep /generalize. Sysprep cannot prepare the image in this scenario. This issue also affects Windows Store apps that come with Windows 8 (such as Mail, Maps, Bing Finance, Bing News, and others). This may occur when you configure an installation in audit mode as a built-in administrator or when a special account is used. The following error appears in the sysprep log files (%WINDIR%\System32\Sysprep\Panther):

was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

Sysprep /generalize requires that all applications be provisioned for all users. However, when you update an app from the Windows Store, the app becomes unprovisioned and account bound.

In this section

When you prepare a Windows image, Windows Setup processes settings during the preparation phase of the configuration. Even if the service computer and the reference computer have the same hardware configuration, you must run the Sysprep command with the /generalize parameter. The Sysprep /generalize command removes unique system information from a Windows installation, making it safe to use the image on another computer. However, you can save the drivers during the setup phase.

Important

When you set up a reference computer, Windows Setup installs drivers for all detected devices. By default, Windows Setup removes these drivers when preparing the system for use. If the image is deployed to computers with the same hardware and devices, you will need to have Windows Setup install the same drivers again. To leave these drivers on the computer during system preparation, set the Microsoft-Windows-pnpsysprep | PersistAllDeviceInstalls true. For more information about the Sysprep-related Windows components that you can add to the answer file, see Unattended Windows Installation Reference.

When you run the Sysprep command, Windows replaces only the computer security identifier (SID) on the operating system volume. When Sysprep prepares an image, only the shared partition is prepared. Therefore, if you have multiple operating systems installed on the same computer, you must Sysprep each image separately.

Preparing the image for use

Add one of the following parameters to your response file.

Use the Microsoft-Windows-Deployment | Generalize. Set Mode to OOBE or Audit and ForceShutdownNow to true. The computer will automatically prepare the image for use and shut down.

Add the Microsoft-Windows-Deployment | Reseal to the oobeSystem configuration stage. Set Mode to Audit. After your computer boots into audit mode and the System Preparation Tool window appears, use one of the following methods:

After shutting down your computer, capture the image using image capture. To do this, you can use the Dism /capture-image command in the Deployment Image Servicing and Management (DISM) tool.

For more information, see Settings to automate startup when you first turn on your computer and Configuring Oobe.xml.

If you need to configure additional settings, you can enter audit mode manually and perform the configuration before you prepare the image for use and deploy it.

Optional action. Entering audit mode manually before preparing the image for use

When the startup screen appears when you turn on your computer for the first time, press CTRL+SHIFT+F3. Windows restarts the computer in Audit mode and the System Preparation Utility window appears.

Attention

The Ctrl+Shift+F3 keyboard shortcut prevents you from skipping all steps in the startup process when you turn on your computer for the first time, such as running scripts and applying answer file settings during the oobeSystem setup step.

Add all the settings you want to enable.

In the System Preparation Utility window, select Prepare for Use and click Shut Down, and then click OK. The computer will prepare the image for use and shut down.

Close the System Preparation Tool window, open a Command Prompt window as an administrator, and navigate to the %WINDIR%\system32\sysprep directory. Use the Sysprep command with the /generalize, /shutdown, and /oobe options. For example:

Sysprep /generalize /shutdown /oobe

The computer will prepare the image for use and shut down.

After shutting down your computer, capture the image using image capture. To do this, you can use the Dism /capture-image command in the DISM tool.

Deploy this image to a reference computer. When you boot your reference computer, the startup screen appears when you turn on the computer for the first time.

For more information about audit mode, see:

In versions of Windows earlier than Windows 8, you can use Sysprep to prepare a virtual hard disk (VHD). However, Windows 8 includes a Sysprep virtual machine mode. Virtual machine mode prepares a virtual hard disk for use in the same virtual machine or in a hypervisor. This mode supports rapid deployment of virtual machines. Virtual machine mode is only supported when running under a virtual machine. In addition, work in virtual machine mode is carried out only on the command line. Virtual machine mode cannot be used to prepare a virtual hard disk for deployment on any computer.

Preparing the virtual hard disk for use

In audit mode, open a command prompt window as an administrator and navigate to the %WINDIR%\system32\sysprep directory.

Use the Sysprep command with the /generalize, /oobe, and /mode:vm parameters. For example:

Sysprep /generalize /oobe /mode:vm

The computer will prepare the virtual hard disk image for use.

Deploy a generic virtual hard disk image to the same virtual machine. When you reboot the virtual machine, the startup screen appears when you turn on your computer for the first time.

The only additional options that are applicable in VM mode are /reboot, /shutdown, and /quit.

Related Sections

Understanding the Sysprep process Sysprep command-line options Sysprep support for server roles Working with product keys and activation

msdn.microsoft.com

Creating your own Windows 10 build. Part 2

Hello everyone, we continue to create our Windows 10 disk image, let me remind you that in the first part we installed ADK, you can see it using the link on the left. Now we will prepare Windows 10 itself, everyone will of course do this for themselves, I will just tell you how I get a clean and updated ten, which differs from MSDN, only with fresh updates, which is very important when reinstalling the system, in view of saving a huge amount of time, which you would spend one hundred percent on installing software and updates.

And so I remind you that we will make ISOs based on the original MSDN Windows 10 threshold 2 (you can download the original Windows 10 image from the link on the left from the Yandex disk). Next, to create your image, you will need either a separate laptop, or best of all, a virtual machine on vmware workstation, the convenience is that everything will be done on one computer and you can easily access it, and the ten installed inside the virtual machine will not affect your main system.

And so we do a clean installation of Windows 10, in my case this is the Professional edition, you can have any other. Now you need to install MS Office and other programs. After which you need to install cumulative Windows 10 updates so that when you try to find new ones, they are missing. After the update, be sure to reboot so that you do not have glitches and problems, the most common are

problems rebooting windows 10
Windows 10 start button not working

If everything is ok with the system, then you can now begin to prepare it for the reference image. A built-in utility called sysprep will help us with this.

Sysprep on Windows 10

And so the sysprep utility helps to depersonalize the Windows system, what does this mean

Removing Unique GUIDs and SIDs
Removing drivers installed for the current operating system

As I wrote above, the utility is built-in and is located along this path.

C:\Windows\System32\Sysprep

Let's launch it.

First of all, it is necessary to audit the system and prepare it for use, set everything as in the picture, if you get the error Sysprep could not verify the Windows installation, then read how to fix it.

The utility will begin running; it may take a minute or more, depending on the speed of the disks.

After running the utility, your operating system will reboot and automatically log in under the Administrator account.

Now, so that you do not have the old account, the next time you install, you need to delete it. To do this, go to Control Panel > User Accounts

Click Manage another account

As you can see, I have an Iva account, I’ll delete it

Select complete deletion without saving data

As a result, you should only have the Administrator account.

And the last step is to select the item in sysprep > Go to the OOBE system welcome window, check the Preparing for use box, and in the Options select Shut down and click OK. The utility will run and turn off your system.

pyatilistnik.org

Sysprep 3.14 has encountered an unrecoverable error on Windows 8.1

Good afternoon, dear readers, as you know, once every three months I try to create fresh images of Windows, both client and server platforms, this time I created everything except Windows 8.1, all because I caught the error Sysprep 3.14 there was an unrecoverable error, I I’ve already seen it in other editions, let’s see how it’s solved in this version.

Sysprep in windows 8.1

I remind you what the sysprep utility is, I give a link to my previous article, since I have already told you everything in detail and there is no point in retelling it. And so, at the moment of depersonalization of the operating system, at the time of the audit mode, I caught this error.

A fatal error occurred while running Sysprep on your computer in Windows 8.1

As I wrote above, I saw this with sysprep in Windows 7 and the error Sysprep could not verify the installation of Windows 10, in the top ten this was already at the oobe step.

As before, any problems with windows sysprep 3.14 are written along the path

C:\Windows\System32\Sysprep\Panther

All this stuff is logged into a file called setuperr.log and setupact.log

Windows sysprep errors

let's see what errors I had.

SYSPRP Failed to remove apps for the current user: 0x80073cf2 > tells you that there is an application for the current user that needs to be removed.
SYSPRP ActionPlatform::ExecuteAction: Error in executing action; dwRet = 0x3cf2
SYSPRP SysprepSession::Execute: Error in executing actions from C:\Windows\System32\Sysprep\ActionFiles
SYSPRP WinMain:Hit failure while processing sysprep cleanup external providers; hr = 0x8007001f
SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 0x1f

All other errors will need to be edited in the Windows registry. Let's start in order with error 0x80073cf2. What applications are we talking about, this is what is in the store, you need to delete them, there are two options, graphical or through powershell.

It is better, of course, to view the list of applications that are interfering with you through Powershell. Open the snap-in and enter the command to import the necessary modules.

Import-Module dism

After the necessary modules are loaded, enter the following command to get the list.

Get-AppxPackage -AllUser | Where PublisherId -eq 8wekyb3d8bbwe | Format-List -Property PackageFullName,PackageUserInformation

As you can see, sysprep in Windows 8.1 interferes with applications for the Administrator account, and they have a PackageFullName by which they can be deleted.

Let's delete them all at once for all users / Built-in applications of Windows 8.1, in this case, are evil, since they cause garbage in Sysprep 3.14 that an unrecoverable error has occurred in Windows 8.1.

Get-AppxPackage -allusers PackageFullName | Remove-AppxPackage

If you want to delete separately, then enter the command:

Remove-AppxPackage -Package

Remove-AppxProvisionedPackage -Online -PackageName