Sysprep
Hi, after using sysprep on my windows 7 OS since I was upgrading my system from Intel Pentium, 2gb ram to Intel core i5, 4gb ram for a new application that I will be using for work but now I'm experiencing
a problem with my internet connection it is extremely slow it even take time to open Google and I'm also getting a java.net error.
It has been a week and I cant work. Please help
Hi,
If you could boot from new processor, please remember to update the corresponding driver for test.
Right click Computer -> Manage -> Device Manager -> Processors, click to expand it's sub entry, right click your processor to select "Update Driver Software..."
In addition, about why your internet connection is so slow, please refer to this article:
Why is my Internet connection so slow?
http://windows.microsoft.com/en-in/windows/why-internet-connection-slow#why-internet-connection-slow=windows-vista
Karen Hu
TechNet Community Support
Similar Messages
-
A Sysprep question on SID changes
Hello,
I have an issue with Sysprep and the Generalize option in WIN 7.
According to all M/S conventional wisdom I need to run this pass to remove COMPUTER NAME and SID's on a machine that I am going to deploy to the field multiple times. I have created on the image a local user with restriction on desktop access
via an LGPolicy. Sort of like a Kiosk in a mall.
When I run the GENERALIZE option, I lose the LGP restrictions on the local user because of the SID change. Now I know after reading a metric-boatload of email and forum threads about being able to copy the .pol files and the USER/MACHINE folders
to the new machine... basically I've tried and it doesn't really work without alot of extra work after the fact. Now I know stuff like this can be scripted for automation... but I would like to shake the trees and get a response from the
community to this thought...
Why do I need to change the SID's on a machine that will NEVER connect to the network behind the firewall, only thru a VPN. All applications a client/server based and or Web based. So there is no need to ID the machine or the user. Since the
user logs in via the VPN. It is joined to the domain upon Imaging for any updates etc.. and registered in AD, but after that it will NEVER touch the domain unless it is through a VPN. SO WHY RUN THE GENERALIZE PASS AT ALL?? Other than changing
the computer name.. which I can do elsewhere. I dont need the SID change.
This machine is used as a Mobile Data Terminal in a Public Safety environment, so I want to lock it down and have it autologin to a user upon powerup/reboot. I do this to keep it simple for the officers to use.
I have an Image that works, I just want to clone it to the field.
any thought from the assembled masses??
Warren Harris
City of Dallas Mobile Technology CenterAre you using Windows 7 Embedded or Enterprise?
On a retail desktop OS, there shouldn't be any user accounts created at the time if you deploy your source OS to Audit Mode by default. I would then create a user group and assign policies to that group. Then when you sysprep the machine, the user account
you create, specify the Group name you created (as opposed to Users or Administrators) and see if the changes still remain.
Note that I have not actually set a local security policy in an image before. I just did a test where I disabled the UAC's Secure Desktop while in Audit Mode and did a sysprep/generalize and the setting was NOT lost. I tested on Windows 7 Ultimate SP1 x64. -
Im trying to deploy a reference machine (configured) to other machines (exact or close image) with different hardware.
I have successfully used sysprep in out of the box, generalise, shutdown mode although i havent tried to deploy this to another device. Unfortunately it doesnt copy the profile to default.
I understand that I have to create an answer file using image manager based on that image, save it to a usb drive and attach this in the sysprep command line when sysprepping it.
My problem is I dont know how to easily capture an image of windows 8 into a wim file so that i can add this into image manager to create a answer file. Im also not sure what I have to do in image manager, is it a simple matter of creating and saving
the answer file or do i have to configure it to copy the profile specifically (theres only one account anyhow).
I also want to know if i have to attach the drivers or are all the standard drivers put into the sysprep image as standard. I would like the machine to be an exactly replica, same as doing a clone (but with the drivers for the new machine installed
so it will boot) same as doing a clone and then repair? If thats possible.
Any specific instructions on this would be helpful. I have read the microsft links but they are somewhat confusing.I know this is a very late response but I thought I'd post for others who search.
The easiest way to create the .wim file is via WinPE, this guy's two YouTube videos explain the entire process in detail -
Windows 8 ADK Part 1: Capture an OS image - https://www.youtube.com/watch?v=XJ8zKX_8E9w
Windows 8 ADK Part 2: Windows Image Deployment - https://www.youtube.com/watch?v=HHIvoqSw_FI
Here's a quick rundown from my notes:
WINPE
Create WinPE via imaging tools command prompt
copype amd64 c:\winpe
makewinpemedia /iso "c:\winpe" "c:\winpe\winpe64.iso"
UNATTEND
Open Windows System Image Manager
Configure unattend.xml
Save unattend.xml to sysprep folder
Create script and save it to sysprep folder to launch sysprep with unattend
@echo off
cd C:\Windows\System32\sysprep
Sysprep /oob /generalize /unattend:C:\Windows\System32\sysprep\unattend.xml
SYSPREP
C:\Windows\System32\Sysprep
Run as administrator
OOBE/Generalize
Shutdown
CONFIGURATION of WINPE
Set IP - netsh int ip set address "Local Area Connection" static 192.168.1.2 255.255.255.0 192.168.1.1
Set DNS - netsh int ip set dns name = "Local Area Connection" source = static addr = 192.168.1.4 validate = no
Map Network Name - net use z:
\\WindowsADK\reflex\images password /USER:domain.local\username
DISKPART
diskpart
list disk
select disk zero
list partition
select partition 2 (OS partition #)
Assign letter=S (assigns drive letter to partition)
Exit
DISM
dism /capture-image /imagefile:z:\image.wim /capturedir:s:\ /name:"Windows 8.1 Custom"
Verify image is saved in the image share (z:)
http://www.microsoftfanboys.com -
Windows 8 Sysprep - Can't skip local account creation and autologon fails, wrong admin password.
Using Windows 8 x64 Enterprise, Sysprep pauses to ask me to create a local user, which I don't want.
If I enable SkipSystemOOBE and SkipUserOOBE in OOBE under Microsoft-Windows-Shell-Setup sysprep (in oobe mode) will skip user creation and autologon works. But it only works correctly once. If I run sysprep again, when it tries to autologon
it will say that I have the wrong password for the local account. After I type in the password manually it works. If I use the same password for the local administrator account as for the autologon account, it looks to have the encrypted password
twice with an equal sign after it.
What I need to know:
How to skip local user account creation (we run on a domain but I have it connect through scripts later)
How to fix the autologon issue
Do I need the local administrator account enabled for this to work?
I have my unattend.xml file attached.
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<AutoLogon>
<Password>
<Value>[removed]</Value>
<PlainText>false</PlainText>
</Password>
<Username>[removed]</Username>
<LogonCount>2</LogonCount>
<Enabled>true</Enabled>
</AutoLogon>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<Order>1</Order>
<CommandLine>c:\folder\abatchfile.bat</CommandLine>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
</FirstLogonCommands>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
<HideOnlineAccountScreens>true</HideOnlineAccountScreens>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<NetworkLocation>Work</NetworkLocation>
<HideLocalAccountScreen>true</HideLocalAccountScreen>
<ProtectYourPC>3</ProtectYourPC>
</OOBE>
<TimeZone>Eastern Standard Time</TimeZone>
<DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet>
<RegisteredOrganization>Company Name</RegisteredOrganization>
<RegisteredOwner>CompanyName</RegisteredOwner>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<UserLocale>en-US</UserLocale>
<UILanguage>en-US</UILanguage>
<SystemLocale>en-US</SystemLocale>
<InputLocale>en-US</InputLocale>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ComputerName>*</ComputerName>
</component>
</settings>
<cpi:offlineImage cpi:source="wim:[removed]/sources/install.wim#Windows 8 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>The user accounts-creation page in Windows Welcome is suppressed if a user or a group is added to a local security group. Add a user or a group to a local security group by doing one of the following:
Create a local user.
Add a domain user to a local security group with the Microsoft-Windows-Shell-Setup | UserAccounts unattended installation setting.
To suppress the user accounts-creation page in Windows Welcome, without creating a local user, use one of the following workarounds:
Workaround 1
If the computer is already joined to a domain, use the following XML example to add the Domain Users security group to the Local Users security group.
<DomainAccounts>
<DomainAccountList wcm:action="add">
<DomainAccount wcm:action="add">
<Group>Users</Group>
<Name>Domain Users</Name>
</DomainAccount>
<Domain>FabrikamDomain</Domain>
</DomainAccountList>
</DomainAccounts>
Because joining a domain automatically adds the Domain Users security group to the Local Users security group, the DomainAccounts command does not affect the membership of the Local Users group. However, using this XML example to join a domain will also suppress
the user accounts-creation page in Windows Welcome.
Workaround 2
Use the Sysprep/Quit command to set the following registry value to 1:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OOBE\UnattendCreatedUser
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ” -
Sysprep unattend file not applying when image is captured with wds (no errors)
So I've been around the block a bit using sysprep and wds. Recently I've created a reference image with a virtualbox environment using windows 7 x64. I was succesfully able to create a reference image, sysprep it and capture it to the wds server. My
plan there after was to create driver specific images for each model computer we use here after not having much success using the driver store (another story)
Any how So I take my reference image and deploy it to a new computer... In this case an HP Probook 5310m. Install any missing drivers and Sysprep it with the following command. sysprep /generalize /oobe /unattend:unattend.xml /shutdown
Below is the sysprep file I have been using
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="generalize">
<component name="Microsoft-Windows-Security-SPP" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SkipRearm>0</SkipRearm>
</component>
<component name="Microsoft-Windows-PnpSysprep" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DoNotCleanUpNonPresentDevices>true</DoNotCleanUpNonPresentDevices>
<PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SkipAutoActivation>true</SkipAutoActivation>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ShowWindowsLive>false</ShowWindowsLive>
<TimeZone>Eastern Standard Time</TimeZone>
<CopyProfile>true</CopyProfile>
<ProductKey>74fdj-7dtw8-q9mp9-ypth8-qb27y</ProductKey>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<OEMInformation>
<Logo>c:\windows\system32\oemlogo.bmp</Logo>
<SupportHours>Regular Business Hrs (Overnight Support Provided)</SupportHours>
<SupportURL>url</SupportURL>
<SupportPhone>Phone number</SupportPhone>
</OEMInformation>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
<HideWirelessSetupInOOBE>false</HideWirelessSetupInOOBE>
</OOBE>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>TAAxAEQAMwBzAHQAcgBpACEAUABhAHMAcwB3AG8AcgBkAA==</Value>
<PlainText>false</PlainText>
</Password>
<Description>Local Administrator</Description>
<DisplayName>Root</DisplayName>
<Group>Administrators</Group>
<Name>Root</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<TimeZone>Eastern Standard Time</TimeZone>
<ShowWindowsLive>false</ShowWindowsLive>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<Order>1</Order>
<CommandLine>slmgr.vbs /ipk {serial key}</CommandLine>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<Order>2</Order>
<CommandLine>slmgr.vbs /ato</CommandLine>
</SynchronousCommand>
</FirstLogonCommands>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>en-US</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UILanguageFallback>en-US</UILanguageFallback>
<UserLocale>en-US</UserLocale>
</component>
</settings>
<cpi:offlineImage cpi:source="catalog:v:/sources/install_windows 7 professional.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
The machine succesfully syspreps and shuts down. I restart the computer pxe boot and capture the image succesfully.
Now here comes my problem...
Upon deploying the above driver specific image.. my sysprep file is not applied. Nothing from the OOBE wizard answers to the pc logo , or first logon commands are applied ... nothing.. I have gotten no errors during this whole process. I have
started to try to read the logs within the panther folder but havent gotten far.
What is weird to me is that I have tried recreating this image... deploy the reference image... add drivers ... sysprep ...shutdown. And if I boot normally (without capturing the image) the computer shows all of the sysprep changes.. Only when
i capture the image does it not apply the changes....
I'm stumped...
Any ides?Confirm this scenario: You installed Windows, then ran sysprep and used the /unattend switch. Then you captured the image.
In this scenario there are 2 deployment methods.
1. If you deploy the image with DISM, the answer file generated by sysprep is detected on first boot and settings are applied. It is the same function as if you ran sysprep and chose to restart.
2. If you deploy the image using Setup.exe, it does not use the answer file specified by sysprep prior to capturing. I have not looked into *why* this happens, but I suspect that after the image is applied, it replaces the unattend.xml with the generic one.
If you are using Setup.exe, you need to use its /unattend switch and point to the answer file location. This location cannot be inside of the image. If you are not using setup.exe in a manual method (using WDS) you will need to apply the answer file to the
install image in the WDS snap-in. -
Reboot before sysprep when I want to add an installation task with Office 2013
Hi all,
I want to buid a reference computer with a genuine Win7 wim file, correct drivers, uptodate patches, and usefull applications. So I use a “Build and Capture Task Sequence”. The new reference image captured, I can use it with WDS or a media
to any computers, using a second and different “Build and Capture Task Sequence.”
All things were right, I could add Acrobat Reader, Java and some others application, but it failed when I tried to add “Add Application Task” with Office 2013. I could import the software, I discovered the new panel to configure config.xml
and mychoice.msp, but when I run the Tasq sequence, when it begin to sysprep the OS, a few time before the capture, the computer reboots. Sysprep does not run, and the image is not captured.
I can add any software installation in the Tasq sequence but not one with Office 2013.
What do you think about this issue?Hi,
Some pieces of advice, since I have managed to create a Windows 7 WIM file with Office 2013 embedded without any problems:
Build your reference image in a virtual machine, not on physical hardware, to prevent a gigantic driverstore with drivers for one or more models, and having to rebuild your image every single time you use a new model. This is not how MDT works, MDT works
hardware agnostic, since it inject's drivers of hardware for each model before the WIM file is applied to your target computer.
Do you really want to embed applications like Adobe Reader and Java in the image? They have a release every month. Do you want to (or is there room for) updating your image every single month? Put them in the deployment phase of your task sequence. This
way these applications are left out the WIM file, but are installed after the WIM file is applied to your system. Yes this takes a little bit more time when deploying a machine, but that's time you'll save on not managing your WIM file every single month
Check your
log files, make sure your machine is not Domain Joined, since that is the biggest mistake people make when sysprepping a machine. And check
Setuperr.log for any sysprep errors. Guaranteed it has noting to do with Office 2013
Good luck!
If this post is helpful please click "Mark for answer", thanks! Kind regards -
Office 2013 apps showing templates error after Sysprepping Windows 7 with CopyProfile setting
Here is my setup:
I installed Windows 7 Professional.
I entered Audit Mode (which automatically logged me in as the built-in Administrator user) and installed the entire Office 2013 Professional Plus suite.
In Audit Mode, I opened Word 2013 to get through the "new user" prompts, such as the opening movie that plays in all Office 2013 programs. I did this to ensure that any new users who log into the computer would not need to sit through these "new
user" prompts. I also rearmed Office 2013.
I ran Sysprep with the CopyProfile setting in the Unattend.xml file, with the /generalize switch, and the /oobe switch. The CopyProfile setting copies settings from the built-in Administrator account to any new user who logs into the system.
Both Windows and Office were successfully activated using KMS.
Everything seemed to work, but there is one problem: when any user -- all of which are standard users rather than administrator users -- logs into Windows and runs any Office 2013 program that has templates (such as Word, Excel, and PowerPoint), the templates
on the Start page do not appear. In their place, the following error message appears on the Start page where the templates would normally have been listed:
"Sorry, we had trouble getting the featured templates and can't show them right now."
Below the error message is a link that reads “Work Offline.” If you click the “Work Offline” link, the error message disappears and the templates appear as they should. However, the error message re-occurs when the application is closed and re-opened.
If I login as the built-in Administrator account (i.e., the account I used to modify the default profile), this problem does not occur at all when using Office 2013 programs.
Any ideas?"logs into Windows and runs any Office 2013 program that has templates (such as Word, Excel, and PowerPoint), the templates on the Start page do not appear. In their place, the following error message appears on the Start page where the templates would normally
have been listed:
"Sorry, we had trouble getting the featured templates and can't show them right now." "
Is there any chance to let you skip the Start page for Office application? I mean that try to open Office application (such Word)and go to File > Options > Untick the option "Show the Start screen when this application starts". Try to re-launch
the application again to check if the error still pop-up. If yes, I'm afraid the default build-in template is corrupted somehow and we need to copy a healthy one from another computer or totally rename normal.dotm documents from %userprofile%\AppData\Roaming\Microsoft\template.
Afte that, please check if the issue still persists.
Here is another thread with the similar topic for your reference:
http://social.technet.microsoft.com/Forums/ie/en-US/09a69d4c-9e5f-489d-ba7b-2af79ff83596/deploying-normaldotm-through-oct-doesnt-work-in-office-2013?forum=officesetupdeploy
http://answers.microsoft.com/en-us/office/forum/office_2013_release-office_install/can-not-sign-into-office-2013-version/b6951c25-2fb5-4fc1-a667-2327b9da2f7f
Tony Chen
TechNet Community Support -
X61 - Can't get sysprep'ed image to boot on it.
Scenario
I am the senior desktop analyst in the offices of an international business travel company.
We recently won the Lenovo account and the employee of our company that manages the account needs to use a Lenovo laptop exclusively so I was sent a brand new X61 to configure for the rep.
X61 originally came with Vista preloaded but I slapped XP SP2 on it using the enclosed bootable Rescue CD and six XP recovery CDs.
Since we already use a single working corporate image for the 6 different non-Lenovo hardware platforms we currently use, I want to deploy the same image to this user.
I was the person that created the image from scratch and I see no problem with it actually working on the X61.
To create an image for the laptop, one of our fastest desktops was imaged with our corporate master image and brought up normally as if the PC was being readied for deployment.
Once everything had completed, the HD in the desktop had the proper Lenovo x61 drivers added to it and the SATA drivers added to the sysprep.inf file as well.
After that it was sysprepped, shutdown and left lying in its original desktop ready to be cloned over to the drive in the X61 where it would be booted up for the first time after sysprep, in the X61.
So I would still be able to keep the preload on the x61's original hard drive, I used a SATA laptop hard drive from one of our current non-Lenovo systems for the image transfer to the x61.
Problem
When I clone the sysprepped image from the desktop hard drive over to the laptop hard drive, it refuses to boot in the IBM.
It just sits at the screen with a blinking cursor doing nothing.
Troubleshooting so far
I have put the corporate image on the x61's original hard drive [with the XP preload] by just replacing the original data partition and leaving the recovery partition alone = blinking cursor.
I have cloned the whole source drive over to the Lenovo preload HD, removing the recovery partition completely = blinking cursor.
I have installed XP from the original CD using a USB-floppy drive and the F6 key to add the SATA driver during startup.
Once completely installed, I figured that it had a valid boot sector and I Ghosted over the sysprepped image without the IB switch and I still get the blinking cursor.
I have researched on the Internet using Google and have found a couple of links that seem to indicate what the problem might be and have listed them below
Predesktop Authentication
This has nothing to do with the issue at hand as this option lies in the BIOS under Security,FingerPrint.
Its BIOS description also states that this option decides whether fingerprint access is required to boot the laptop and this option has been in the disabled state even while the laptop was booting the Factory Preload.
SATA set to Compatibility instead of AHCI
This setting only affects how the OS sees the HD, not how the laptop sees it and I tried it anyway and it has no effect.
If your XP image isnt properly sysprepped to handle the SATA drive using the proper driver, you will need to set it to Compatibility mode to get into Windows.
As it stands, this is not an issue as I have edited the sysprep.inf to add the SATA driver reference for this laptop and if it ever boots the image, I expect it to never BSOD but thats if it ever boots which it hasnt so far.
Ghosting using the IB switch
I was SO sure that this would fix the issue but I get the same blinking cursor.
Booting into DOS and using Ghost 8.3, I ran "ghost -ib" and selected the sysprepped desktop drive as the source and the laptop drive as the destination and it still leaves me at the blinking cursor when I try it in the laptop.
Re-creating the MBR
I have done this two different ways, one using Norton GDISK and one using a regular Windows 98 bootdisk.
The Windows 98 bootdisk kept saying "No fixed disks present" so it never worked.
Nortons GDISK didnt have any issues re-creating the MBR on the laptop or on the laptop HD plugged in the desktop but the drive still doesnt boot.
Signature failure error
I have heard about people having the same issue as me and getting this error but so far I have not received this error.
As of now, I have restored the XP SP2 preload back on to the laptop to get the original boot sector back as I believe that is the key to solving this whole nightmare.
There are other things I have tried as well and since I have been at it exclusively for almost two full business days now, everything is much upstairs right now but I will remember what I have tried if anyone wants to e-mail me any suggestions.
I await and welcome anyones advice.
Solved!
Go to Solution.Hi all,
Sorry about not updating this thread but here is the solution and the explanation, hopefully, I dont miss anything because I would like this all in one place so it can be referenced in the future.
The Lenovo's and the Dell's and maybe other OEM's [not Fujitsu-Siemens] use a recovery partition and the boot table that references it is based on some form of Linux as also is the recovery partition itself.
As far as I know, all flavors of Linux use 8,192 bytes for a boot table [4 sectors of 2048 bytes each] whereas a standard boot table is only 1 sector and 2048 bytes long.
This is the reason for the problem that happens with OEM laptops like this one.
What you need to do to get the image to boot is the following [BSODs after booting is another issue]
Create the image to a ghost file on whatever platform you want but use the IB switch in Ghost to create the image with the boot table intact.
Deploy the image to the IBM laptop hard drive ALSO using the IB switch
When doing ANY image deployment to the laptop, the hard drive MUST be IN the laptop itself. The laptop writes its boot sector differently so the hard drive must be in it for the image to work. I was doing everything right but this step and I was still having the issue so this is crucial.
If you are testing the image by deploying straight from the test PC to the laptop by using the Ghost Peer-2-Peer TCP/IP option, start Ghost on both ends with the IB switch but remember the destination SATA drive MUST be in the laptop itself.
Thats it.
Hope this helps everyone out. -
How many times can Windows 7 be syspreped, what is the official Answer?
Hey everyone, can somebody out there give me the straight answer on this? What is the official number windows 7 can be syspreped? I am looking to build my reference images, but every time I do this I have to 150+ updates each time. Can
I get way with just updating the reference image every time? I have heard there is a Max number of times you can do this before you have to rebuild.
We are running WIndows 7 Enterprise with KMS.
Also will this apply to 8.1?
ThanksHi,
Sysprep limitations are due to the windows activation process.
There is no limit to the number of times that the Sysprep command can run on a computer. However, the clock for Windows Product Activation begins its countdown the first time Windows starts. You can use the sysprep /generalize command to reset Windows Product
Activation a maximum of three times. After the third time that you run the sysprep /generalize command, the clock can no longer be reset.
Assuming you are using a KMS: We recommend that KMS clients use the sysprep /generalize command where the value of the SkipRearm setting is equal to 1. After capturing this image, use the sysprep /generalize command, where the value of the SkipRearm setting
is equal to 0.
Karen Hu
TechNet Community Support -
Remote Desktop Connection to VM does not work after sysprep
Hello altogether.
Often asked, but never answered with an applicable solution!
What shall
we
do if
we
get no access to a Azure VM via Remote Desktop
Connection?
Everything went well: access to the VM via RDC was working perfectly!
Then
the idea came into
our
mind to create an image of the VM by use of the Azure Management Portal.
We
found that
we
had to apply “sysprep”
on the VM.
We
did it.
Then we did not take the image and decided to go on with the VM.
But if we start the VM we get no access via RDC!
We tried to find a solution by reviewing the already published contributions by other Azure
users. But none of the replies marked as answered supply with a qualified solution.
So can one provide a really applicable solution to us on how to arrange the further use of the VM?
Thank you in advance.There is an issue right now where the VM may start unexpectedly after you have run sysprep and selected the shutdown option (which is normally what you should do).
http://social.msdn.microsoft.com/Forums/windowsazure/en-US/fafb9ee6-1e57-46ba-8440-27467ad986cf/image-capture-issue-vm-unexpectedly-started-after-guestinitiated-shutdown?forum=WAVirtualMachinesforWindows
But regardless of that issue - you can't use that deployed instance of the VM after you've run sysprep on it. It needs to stay shutdown, then you select Capture to create an image from it.
If you start it back up, either intentionally, or it is started unexpectedly because of the issue above, it will be sitting at the first interactive screen of setup. RDP is not working at that point, and since there is no console access to an Azure VM, there
is no way to get past that prompt.
For other scenarios, you might be able to attach the OS disk of that VM as a data disk to another VM, and while you could do that in this case too, there is no supported method for disabling sysprep at that stage of setup.
So while you could attach it to another VM to get data off of it (you would have to remove the VM first), the VHD is no longer in a supported state to use as a VM itself.
Thanks,
Craig -
I have a base template (which has never been sysprep'd) from which I create linked clones. After the linked clone comes up, I run the following command:
c:\windows\system32\sysprep\sysprep.exe /generalize /oobe /reboot /unattend:c:\windows\panther\unattend.xml
This works fine for the first few linked clones, but after about 3-4 linked clones are running, I start to hit "A fatal error occurred while trying to sysprep the machine."
****c:\windows\panther\setuperr.log****
2013-03-29 16:40:07, Error [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 32[gle=0x00000020]
2013-03-29 16:40:07, Error [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep cleanup providers; hr = 0x80070020[gle=0x00000020]
****c:\windows\panther\unattend.xml****
<?xml version='1.0' encoding='utf-8'?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="oobeSystem">
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>en-US</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UILanguageFallback>en-US</UILanguageFallback>
<UserLocale>en-US</UserLocale>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<AutoLogon>
<Enabled>true</Enabled>
<Username>Administrator</Username>
<Password>
<Value>ca$hc0w</Value>
<PlainText>true</PlainText>
</Password>
</AutoLogon>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>3</ProtectYourPC>
</OOBE>
<UserAccounts>
<AdministratorPassword>
<Value>ca$hc0w</Value>
<PlainText>true</PlainText>
</AdministratorPassword>
</UserAccounts>
<TimeZone>Pacific Standard Time</TimeZone>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ProductKey>7M67G-PC374-GR742-YH8V4-TCBY3</ProductKey>
<ComputerName>*</ComputerName>
</component>
</settings>
</unattend>
****c:\windows\panther\setupact.log****
2013-03-29 16:40:07, Info [0x0f004d] SYSPRP The time is now 2013-03-29 16:40:07
2013-03-29 16:40:07, Info [0x0f004e] SYSPRP Initialized SysPrep log at c:\windows\system32\sysprep\Panther
2013-03-29 16:40:07, Info [0x0f0054] SYSPRP ValidateUser:User has required privileges to sysprep machine
2013-03-29 16:40:07, Info [0x0f0056] SYSPRP ValidateVersion:OS version is okay
2013-03-29 16:40:07, Info [0x0f005e] SYSPRP ScreenSaver:Screen saver was already disabled, no need to disable it for sysprep
2013-03-29 16:40:07, Info [0x0f007e] SYSPRP FCreateTagFile:Tag file c:\windows\system32\sysprep\Sysprep_succeeded.tag does not already exist, no need to delete anything
2013-03-29 16:40:07, Info [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'GENERALIZE'
2013-03-29 16:40:07, Info [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'OOBE'
2013-03-29 16:40:07, Info [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'REBOOT'
2013-03-29 16:40:07, Info [0x0f005f] SYSPRP ParseCommands:Found supported command line option 'UNATTEND'
2013-03-29 16:40:07, Info [0x0f004a] SYSPRP WaitThread:Entering spawned waiting thread
2013-03-29 16:40:07, Info [sysprep.exe] UnattendFindAnswerFile: Looking at explicitly provided unattend file [c:\windows\panther\unattend.xml]...
2013-03-29 16:40:07, Info [sysprep.exe] UnattendFindAnswerFile: [c:\windows\panther\unattend.xml] meets criteria
for an explicitly provided unattend file.
2013-03-29 16:40:07, Info SYSPRP SysprepSearchForUnattend: Using unattend file at [c:\windows\panther\unattend.xml].
2013-03-29 16:40:07, Info SYSPRP SysprepSearchForUnattend: [generalize] pass in unattend file [c:\windows\panther\unattend.xml] either doesn't exist or passed
validation
2013-03-29 16:40:07, Info SYSPRP WinMain:Found unattend file at [c:\windows\panther\unattend.xml]; caching...
2013-03-29 16:40:07, Info SYSPRP WinMain:Processing unattend file's 'generalize' pass...
2013-03-29 16:40:07, Info SYSPRP Sysprep is running a generalize pass with the following unattend file: [%windir%\panther\unattend.xml]
2013-03-29 16:40:07, Info SYSPRP RunUnattendGeneralizePass: Sysprep unattend generalize pass exits; hr = 0x0, hrResult = 0x0, bRebootRequired = 0x0
2013-03-29 16:40:07, Info [0x0f003f] SYSPRP WinMain:Processing 'cleanup' request.
2013-03-29 16:40:07, Error [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 32[gle=0x00000020]
2013-03-29 16:40:07, Error [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep cleanup providers; hr = 0x80070020[gle=0x00000020]
2013-03-29 16:48:52, Info [0x0f004c] SYSPRP WaitThread:Exiting spawned waiting thread
2013-03-29 16:48:52, Info [0x0f0059] SYSPRP ScreenSaver:Screen saver was originally disabled, leaving it disabled
2013-03-29 16:48:52, Info [0x0f0052] SYSPRP Shutting down SysPrep log
2013-03-29 16:48:52, Info [0x0f004d] SYSPRP The time is now 2013-03-29 16:48:52Hi,
This is typical of an OEM license issue.
To avoid this in the future you should look at site/volume licensing.
Anyway.
so, first check if you can re-arm by runing the
slmgr.vbs /dlv and check the re-arm counter, if it set to zero.. you need to do the following :
http://support.microsoft.com/kb/929828 (set the <SkipRearm>1</SkipRearm> like in the example, note: this option will make the product key window to appear in the setup process).
you can also try running : slmgr.vbs -rearm, to rearm Windows.
after that, let's come back to the sysprep process.. for syspreping already syspreped machine we have to change few keys in the registry :
HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus\GeneralizationState\
CleanupState:2
HKEY_LOCAL_MACHINE\SYSTEM\Setup\Status\SysprepStatus\GeneralizationState\
GeneralizationState:7
After done with the registry, do the following :
Start -> Run : msdtc -uninstall (wait few seconds)
Start -> Run : msdtc -install (wait few seconds)
Restart the machine
Check the registry for the right registry keys values
sysprep with the new XML answerfile.
Source: Olegm
If you find my information useful, please rate it. :-) -
Sysprep - Fatal error occurred while trying to sysprep the machine
On the 4th attempt to sysprep a Windows 7 Enterprise system, I get the dreaded, 'A fatal error occurred while trying to sysprep the machine.'
The setuperr.log shows:
2010-08-04 13:57:58, Error [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 31
2010-08-04 13:57:58, Error [0x0f00ae] SYSPRP WinMain:Hit failure while processing sysprep cleanup external providers; hr = 0x8007001f
I've seen articles referring to the Windows Software Licensing Rearm program may have issues running more than three times in a single Windows image and to add <SkipRearm>1</SkipRearm> in the /unattend file... but this did not help.
The Windows Media Player Network Sharing Service has also been disabled which is often referred to in other posts.
The KB article: http://support.microsoft.com/kb/947212/en-us indicated that the resolution is to re-create the image for the machine... This is very frustrating. I'm hoping that there is
a better resolution???
How do you sysprep a machine more than three times to avoid this error?
Thanks!!
930193I had a problem Where Runing slmgr /dlv returned 0 and could not sysprep a
32 bit Win 7 Installed on C:drive
Here is what I did to succeed whit Sysprep.
Disable UAC
Based on
This :
open notepad and copy paste the following:
@ECHO OFF
setLocal Enabledelayedexpansion
for %%d in (c d e f g h i j k l m n o p q r s t u v w x y z) do (
if exist %%d:\windows\system32 (
SET drv1=%%d:\windows\system32
reg load HKLM\MY_SYSTEM !drv1!
reg delete HKLM\MY_SYSTEM\WPA /f
reg unload HKLM\MY_SYSTEM
GOTO END
:END
ECHO Done, Rebooting system...
timeout 3
wpeutil reboot
Then in notepad chose file>save as, in File Type select "All Files", name it "c:\reset.bat"
Reboot Your Pc, after bios screen press F8, Select "Repair Your Computer", select your keyboard layout, enter your credentials if needed,
then select the last option "Open Command Prompt"
type "c:\reset.bat" or "d:\reset.bat" (Sometimes Your Windows Partition get a different letter on the repair environment)
Back on Windows follow step five if needed.
Check under slmgr /dlv you have more than 0 under "Remaining Windows Rearm count"
Download pstools.zip from
here, extract content an copy psexec.exe to %windir%\System32
run psexec.exe and accept the license agreement so it won't bother when running afterwards, close it.
open notepad and copy paste the following:
@ECHO OFF
echo Stopping Windows Media Player Sharing Service..
echo.
net stop wmpnetworksvc
echo.
echo Deleting Old Sysprep Logs...
echo.
del /f /s /q %windir%\System32\sysprep\panther\*.*
echo.
echo Adding Required Sysprep Registry Keys...
echo.
REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform" /v SkipRearm /t REG_DWORD /d 00000001 /f
REG ADD HKLM\SYSTEM\Setup\Status\SysprepStatus /v GeneralizationState /t REG_DWORD /d 00000007 /f
REG ADD HKLM\SYSTEM\Setup\Status\SysprepStatus /v CleanupState /t REG_DWORD /d 00000002 /f
psexec -i -s REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Cleanup /v "{EC9FE15D-99DD-4FB9-90D5-5B56E42A0F80}" /t REG_SZ /d "C:\\Windows\\System32\\iesysprep.dll,Sysprep_Cleanup_IE" /f
psexec -i -s REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Generalize /v "{EC9FE15D-99DD-4FB9-90D5-CE53C91AB9A1}" /t REG_SZ /d "C:\\Windows\\System32\\iesysprep.dll,Sysprep_Cleanup_IE" /f
psexec -i -s REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Specialize /v "{EC9FE15D-99DD-4FB9-90D5-676C338DC1DA}" /t REG_SZ /d "C:\\Windows\\System32\\iesysprep.dll,Sysprep_Cleanup_IE" /f
echo.
echo Uninstalling MSDTC...
echo.
msdtc -uninstall
timeout 10
echo.
echo Reinstalling MSDTC...
echo.
msdtc -install
timeout 10
echo.
echo Cross Your Fingers, Finally Running Sysprep...
echo.
%windir%\System32\sysprep\sysprep /generalize /oobe /shutdown /unattend:unattend.xml
Change Last Line to suit your needs, ie: if you are not using an unnattend answer file, then delete /unattend:unattend.xml"
Then in notepad chose file>save as, in File Type select "All Files", name it "%windir%\System32\do.cmd"
if you use an unattend.xml file copy it to %windir%\System32\sysprep folder.
Once you are ready run %windir%\System32\do.cmd
Hope it helps, -
Error with syspreped windows 7 image related to capisp.dll execution...
Hi Folks,
some time ago I crafted an windows 7 image with sysprep generalization for WDS deployment. In real there are 2 images: one dumped w/o sysprep and the another w/ (dumping with ImageX Tool from WAIK for W7/W2K8R2). The syspreped one I delivered to our WDS
Server. In the past I made several changes based on the non-syspreped image (incl. WUs) and afterward I've generated a new syspreped version from it. ...and now, since the last revision und sysprep run the last syspreped version (stored at the WDS) is no longer
installable onto any target machine... Ervery time I tried to deploy this version from the WDS at the target machine an error popup occurs and says that this image cannot be installed at this target machine type (see *** - the german message). Examinig the
SETUPACT.LOG / SETUPERR.LOG files the following problem has been stated:
2010-06-21 14:22:54, Info [0x0f0081] SYSPRP LaunchDll:Successfully executed 'C:\Windows\System32\sppnp.dll,Sysprep_Specialize_Pnp' without error
2010-06-21 14:22:54, Info [0x0f008b] SYSPRP RunRegistryDlls:Found entrypoint in registry at SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\SysPrep\Specialize\{2172c981-2c23-e969-b30d-046ffeeb096e}; will try to launch 'C:\Windows\system32\capisp.dll,CryptoSysPrep_Specialize'
2010-06-21 14:22:54, Info [0x0f0080] SYSPRP LaunchDll:Found 'C:\Windows\system32\capisp.dll,CryptoSysPrep_Specialize'; executing it
2010-06-21 14:22:54, Info capisp.dll::CheckIFCryptoSysPrepSpecialized: returning 0
2010-06-21 14:22:55, Info capisp.dll::CryptoSysPrep_Specialize: assigned CAPI machine guid "44d42aa2-dee4-4023-bea5-d2f166bbb42c"
2010-06-21 14:22:55, Info capisp.dll::DisableAdministratorIfApplicable disabled the admin account.
2010-06-21 14:22:55, Info capisp.dll::CryptoSysPrep_Specialize: returning 5
2010-06-21 14:22:55, Error [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'C:\Windows\system32\capisp.dll,CryptoSysPrep_Specialize', returned error code 5[gle=0x000003e5]
2010-06-21 14:22:55, Info IBS Callback_Specialize: Internal Providers Specialized Failed. System can't proceed to handle Internal Providers
2010-06-21 14:22:55, Info IBS Callback_Specialize: Specialize return: [5]
2010-06-21 14:22:55, Error [0x060435] IBS Callback_Specialize: An error occurred while either deciding if we need to specialize or while specializing; dwRet = 0x5
2010-06-21 14:22:55, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [***Windows kann nicht für die Ausführung auf der Hardware dieses Computers konfiguriert werden.]
The mentioned error is the only one.
ANY help is very appreciated!
From Colonel GizmoHi,
Regarding the returned error code, error code 0x5 is a “Access denied” error. It seems that the sysprep disables the administrator account, it can’t
process the capisp.dll and pass CryptoSysPrep_Specialize. To resolve this kind of issue, I would like to suggest:
1.
Ensure that you deploy image running as Administrator account.
2.
Mount the image and check if the capisp.dll file exists and try taking ownership of it.
3.
Open Registry Editor and navigate to the following path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Specialize
Check if there is an entry with the Data:
C:\Windows\system32\capisp.dll,CryptoSysPrep_Specialize , make sure it is spelled correctly and check the permissions on the above key.
4.
Then deploy again.
Best Regards
Dale
Please remember to click “Mark as Answer” on the post that helps you. -
Hi There,
I have a Lenovo x240 and i have installed a fresh copy of W8 on it (without any key since we install license keys individually). What i basically do is to download and run Lenovo System Update which downloads and installs chipset drivers automatically. Once
this is completed i run sysprep with command: sysprep /generalize /oobe /shutdown (we do not use any answer file) and proceed to capture the image afterwards. This has been working fine with laptops/computers running Windows7. It is not the case with Windows
8 though.
I have check the setuperr file for errors and states that is failing to secure drivers (intel\openCl). Error is below:
Any suggestions on how to resolve this issue are greatly appreciate it.
ERROR IS:
2014-01-10 09:44:42, Error [0x0f00a4] SYSPRP WinMain: Unable to parse command-line arguments to sysprep; GLE = 0x0
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clang_compiler64.dll. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfne9.rtl. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfne9_img_cbk.o. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfne9_img_cbk.rtl. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnh8.rtl. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnh8_img_cbk.o. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnh8_img_cbk.rtl. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnl9.rtl. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnl9_img_cbk.o. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnl9_img_cbk.rtl. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\cpu_device64.dll. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\intelocl64.dll. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\OclCpuBackend64.dll. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\task_executor64.dll. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\tbb\tbb.dll. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\tbb\tbbmalloc.dll. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\__ocl_svml_e9.dll. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\__ocl_svml_h8.dll. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\__ocl_svml_l9.dll. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clang_compiler32.dll. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfng9.rtl. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfng9_img_cbk.o. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfng9_img_cbk.rtl. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfnn8.rtl. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfnn8_img_cbk.o. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfnn8_img_cbk.rtl. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfns9.rtl. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfns9_img_cbk.o. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfns9_img_cbk.rtl. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\cpu_device32.dll. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\intelocl32.dll. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\OclCpuBackend32.dll. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\task_executor32.dll. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\tbb\tbb.dll. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\tbb\tbbmalloc.dll. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\__ocl_svml_g9.dll. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\__ocl_svml_n8.dll. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\__ocl_svml_s9.dll. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\llvm_release_license.txt. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\readme.txt. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\version.ini. Err = 0x3
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files\Realtek\Audio\HDA\AERTSr64.exe. Err = 0x2
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Windows\system32\drivers\intelaud.sys. Err = 0x2
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Windows\System32\drivers\iwdbus.sys. Err = 0x2
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Windows\system32\igfxsrvc.exe. Err = 0x2
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Windows\system32\igfxtray.exe. Err = 0x2
2014-01-10 09:47:18, Error SYSPRP SPPNP: Failed to secure driver file C:\Windows\system32\RTSnMg64.cpl. Err = 0x2
2014-01-10 09:52:20, Error [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 0x1f
2014-01-10 09:52:20, Error SYSPRP WinMain:Hit failure while processing sysprep re-specialize internal providers; hr = 0x8007001f
2014-01-10 10:26:15, Error [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 0x1f
2014-01-10 10:26:15, Error [0x0f00ae] SYSPRP WinMain:Hit failure while processing sysprep cleanup external providers; hr = 0x8007001f
2014-01-10 10:30:06, Error [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysPrepDtcCleanup' from C:\Windows\system32\msdtcprx.dll; dwRet = 0x80100101[gle=0x000000b7]
2014-01-10 10:30:06, Error SYSPRP ActionPlatform::ExecuteAction: Error in executing action; dwRet = 0x80100101[gle=0x000000b7]
2014-01-10 10:30:06, Error SYSPRP ActionPlatform::ExecuteActionList: Error in execute actions; dwRet = 0x80100101[gle=0x000000b7]
2014-01-10 10:30:06, Error SYSPRP SysprepSession::Execute: Error in executing actions from C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml; dwRet = 0x80100101
2014-01-10 10:30:06, Error SYSPRP RunPlatformActions:Failed while executing SysprepSession actions; dwRet = 0x80100101
2014-01-10 10:30:06, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x80100101
2014-01-10 10:30:06, Error [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep cleanup providers; hr = 0x80100101I am also getting this SAME error on a Microsoft Surface Pro 2 that is brand new out of the box with no updates applied to it whatsoever.
I literally open computer, configure prefs... then sysprep with generalize.
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clang_compiler64.dll. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfne9.rtl. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfne9_img_cbk.o. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfne9_img_cbk.rtl. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnh8.rtl. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnh8_img_cbk.o. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnh8_img_cbk.rtl. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnl9.rtl. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnl9_img_cbk.o. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\clbltfnl9_img_cbk.rtl. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\cpu_device64.dll. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\intelocl64.dll. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\OclCpuBackend64.dll. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\task_executor64.dll. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\tbb\tbb.dll. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\tbb\tbbmalloc.dll. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\__ocl_svml_e9.dll. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\__ocl_svml_h8.dll. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x64\__ocl_svml_l9.dll. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clang_compiler32.dll. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfng9.rtl. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfng9_img_cbk.o. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfng9_img_cbk.rtl. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfnn8.rtl. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfnn8_img_cbk.o. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfnn8_img_cbk.rtl. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfns9.rtl. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfns9_img_cbk.o. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\clbltfns9_img_cbk.rtl. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\cpu_device32.dll. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\intelocl32.dll. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\OclCpuBackend32.dll. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\task_executor32.dll. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\tbb\tbb.dll. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\tbb\tbbmalloc.dll. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\__ocl_svml_g9.dll. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\__ocl_svml_n8.dll. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\bin\x86\__ocl_svml_s9.dll. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\llvm_release_license.txt. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\readme.txt. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\Program Files (x86)\Common Files\Intel\OpenCL\version.ini. Err = 0x3
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\windows\system32\drivers\intelaud.sys. Err = 0x2
2014-01-20 11:13:51, Error SYSPRP SPPNP: Failed to secure driver file C:\windows\System32\drivers\iwdbus.sys. Err = 0x2 -
Fatal error while running sysprep on Windows 7
Ok, so I spent 2 weeks building this Windows 7 image, which now seems to be doing everything almost exactly as I want it. I have my unattend.xml file that I've built for past images that I copied onto this machine, and I ran sysprep with the /generalize
and /oobe flags. I get the above error once it gets into the generalize phase.
The log has the following interesting lines:
WindowsSideShow: Failed to get task folder (0x80070002)
LaunchDll:Failure occurred while executing 'C:\Windows\System32\AuxiliaryDisplayClassInstaller.dll,WindowsSideShow_Sysprep_Generalize', returned error code 31
So, I apparently unwittingly installed some Microsoft network-aware application that either doesn't support or is thoroughly confused by the Sysprep_Generalize command. Fortunately, I have enough experience with Windows to know you make a full disk
image before running a command that can so easily ruin all your hard work. Even though I only waste 20 minutes each time I have to restore an image, it's still frustrating dealing with such an obscure error. Asking The Google only shows obscure
recommendations about rearms (not the issue here) or disabling the Windows Media Player Network sharing service (or something similar....also not the issue here). I could just remove the above mentioned DLL from the generalize steps in the registry,
but I'd like to solve the root problem so my image isn't hiding a sleeper bug.Hi,
If this is not an issue with rearm, please delete keys under this path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Generalize\
And then run sysprep again to check how it works.
Alex Zhao
TechNet Community Support -
Hi guys,
I am trying to make a 64-bit win7 image, but for some reason when I run sysprep I get this error "sysprep a fatal error occurred while trying to sysprep the machine". I have checked my unattend.xml file and all seems fine. I have pasted the sysprep log file below as well as my unattend.xml file. Any help would be much appreciated. Thanks!
setuperr.log file
Code:
2014-02-06 09:38:52, Error [0x0f0043] SYSPRP WinMain:The sysprep dialog box returned FALSE2014-02-06 11:12:12, Error [0x0f0043] SYSPRP WinMain:The sysprep dialog box returned FALSE
2014-02-07 11:41:15, Error [0x0f0043] SYSPRP WinMain:The sysprep dialog box returned FALSE
2014-02-10 06:44:28, Error [0x0f0043] SYSPRP WinMain:The sysprep dialog box returned FALSE
2014-02-10 08:15:43, Error [0x0f0060] SYSPRP ParseCommands:Found unsupported command line option '/?'[gle=0x000036b7]
2014-02-10 08:15:43, Error [0x0f00a4] SYSPRP WinMain: Unable to parse command-line arguments to sysprep; GLE = 0x36b7[gle=0x000036b7]
2014-02-10 08:32:48, Error [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'drmv2clt.dll,Sysprep', returned error code -2147024864[gle=0x00000020]
2014-02-10 08:32:48, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = -2147024864[gle=0x00000020]
2014-02-10 08:32:48, Error [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep cleanup providers; hr = 0x80070020[gle=0x00000020]
unattend.xml file
Code:
<unattend xmlns="urn:schemas-microsoft-com:unattend"><servicing>
<package action="configure">
<assemblyIdentity name="Microsoft-Windows-Foundation-Package" version="6.1.7600.16385" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language=""/>
<selection name="MediaCenter" state="false"/>
<selection name="WindowsGadgetPlatform" state="false"/>
</package>
</servicing>
<settings pass="specialize">
<component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="Microsoft-Windows-Deployment" processorArchitecture="amd64"publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Order>1</Order>
<Path>Net user administrator /active:yes</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
<component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="Microsoft-Windows-IE-InternetExplorer"processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<BlockPopups>no</BlockPopups>
<CompanyName>Lifespace Communities</CompanyName>
<DisableFirstRunWizard>true</DisableFirstRunWizard>
<DisableDevTools>true</DisableDevTools>
<Home_Page>www.lifespacecommunities.com</Home_Page>
<LockToolbars>true</LockToolbars>
<NoDial>true</NoDial>
<SuggestedSitesEnabled>false</SuggestedSitesEnabled>
<DisableOOBAccelerators>true</DisableOOBAccelerators>
</component>
<component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="Microsoft-Windows-Shell-Setup"processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<BluetoothTaskbarIconEnabled>false</BluetoothTaskbarIconEnabled>
<ComputerName/>
<CopyProfile>true</CopyProfile>
<DoNotCleanTaskBar>true</DoNotCleanTaskBar>
<ProductKey>*****************</ProductKey>
<RegisteredOrganization>Lifespace Communities</RegisteredOrganization>
<RegisteredOwner>Lifespace</RegisteredOwner>
<ShowWindowsLive>false</ShowWindowsLive>
<TimeZone>Central Standard Time</TimeZone>
<StartPanelOff>true</StartPanelOff>
</component>
<component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="Microsoft-Windows-UnattendedJoin"processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<Identification>
<JoinWorkgroup>LIFESPACE</JoinWorkgroup>
</Identification>
</component>
<component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="Security-Malware-Windows-Defender"processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<DisableAntiSpyware>true</DisableAntiSpyware>
</component>
</settings>
<settings pass="offlineServicing">
<component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="Microsoft-Windows-LUA-Settings"processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<EnableLUA>false</EnableLUA>
</component>
</settings>
<settings pass="generalize">
<component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="Microsoft-Windows-Security-SPP"processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<SkipRearm>1</SkipRearm>
</component>
</settings>
<settings pass="oobeSystem">
<component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="Microsoft-Windows-International-Core"processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<InputLocale>en-us</InputLocale>
<SystemLocale>en-us</SystemLocale>
<UILanguage>en-us</UILanguage>
<UILanguageFallback>en-us</UILanguageFallback>
<UserLocale>en-us</UserLocale>
</component>
<component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="Microsoft-Windows-Shell-Setup"processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<AutoLogon>
<Password>
<Value>
</Value>
<PlainText>false</PlainText>
</Password>
<Enabled>true</Enabled>
<LogonCount>3</LogonCount>
<Username>administrator</Username>
</AutoLogon>
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<CommandLine>cscript //b C:\Windows\system32\slmgr.vbs /ipk</CommandLine>
<Order>1</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<CommandLine>
%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe -Command "&{set-executionpolicy RemoteSigned -Force}"
</CommandLine>
<Order>2</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<CommandLine>C:\Windows\OEM\SETUP\Drivers\DPINST64.exe /q</CommandLine>
<Order>3</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<CommandLine>
%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe "C:\Windows\OEM\SETUP\Win7Image-Script1.ps1"
</CommandLine>
<Order>4</Order>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
</FirstLogonCommands>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Home</NetworkLocation>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<ProtectYourPC>3</ProtectYourPC>
</OOBE>
<UserAccounts>
<AdministratorPassword>
<Value>
</Value>
<PlainText>false</PlainText>
</AdministratorPassword>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>
</Value>
<PlainText>false</PlainText>
</Password>
<Description>administrator</Description>
<DisplayName>administrator</DisplayName>
<Group>administrators</Group>
<Name>administrator</Name>
</LocalAccount>
<LocalAccount wcm:action="add">
<Password>
<Value>
</Value>
<PlainText>false</PlainText>
</Password>
<Description>presentation</Description>
<DisplayName>presentation</DisplayName>
<Group>administrators</Group>
<Name>presentation</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<VisualEffects>
<FontSmoothing>On</FontSmoothing>
</VisualEffects>
<WindowsFeatures>
<ShowMediaCenter>false</ShowMediaCenter>
<ShowWindowsMediaPlayer>true</ShowWindowsMediaPlayer>
<ShowInternetExplorer>true</ShowInternetExplorer>
</WindowsFeatures>
<RegisteredOrganization/>
<RegisteredOwner/>
</component>
<component xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="Microsoft-Windows-Sidebar" processorArchitecture="amd64"publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS">
<SidebarOnByDefault>false</SidebarOnByDefault>
<SidebarVisible>false</SidebarVisible>
</component>
</settings>
<cpi:offlineImage xmlns:cpi="urn:schemas-microsoft-com:cpi" cpi:source="wim:p:/ot/win7%20imaging/add-on's%20and%20images/win7%2064-bit/sysprep/win7%20cd%20files/sources/install.wim#Windows 7 PROFESSIONAL"/>
</unattend>AH HA!!!! I found the answer! For future issues, I found the answer in the link below. Long story short, Windows Media Player Network Sharing Service was causing sysprep to fail. Had to disable the service, ran sysprep again and all was happy happy. Leave it to Microcrap to break their own products. Thanks for the help Anders!! I really appreciate it!
source:
http://sidecar.twocanoes.com/forums/...atal-error-/p1
4th post
Maybe you are looking for
-
Performance issue - Loading and Calculating
Hi,<BR>I am having 5 GB of data. It is taking 1 hr to load and 30 min to calculate. <BR>I did the following things to improve the performance.<BR>1) Sort the data and loading them in the order of largest sparse first, followed by smallest and dense<B
-
Is there any way to stop the output of the iMac display to a connected TV?
I just bought an iMac 21.5 and successfully connected it to my plasma HDTV using a Mini Displayport to HDMI adaptor and HDMI cables. Ideally, I would like to have the HDTV set up as a second display for watching movies, rather than mirroring the two
-
"Edit in Photoshop": Why is Photoshop is greyed out?
I have LR 3.2 and PS CS5 Extended installed on a Win 7 64 bit PC. Preferences|External Editing shows Photoshop but when I choose an image and right click, Edit in shows Photoshop greyed out. (Also when chossing Edit In from the Photo drop-down menu
-
I have a solution with 9 projects, the application compiles with no errors; when I run the startup project which calls a property in another project in the solution; I will get the following error System.TypeInitializationException was unhandled Me
-
Does XMLSQL Utility support JDBC-ODBC brideg?
Dear Sir, I want to use your XMLSQL Utility to exchange data between XML and database( Access database ) through sun's jdbc-odbc bridge, but got the following run time error: oracle.xml.sql.OracleXMLSQLException: java.lang.ClassCastException: sun.jdb