After having a few issues with Windows Media Player 11 and sysprep (reseal) on XPSP2not playing well together (had to uninstall WMP11 to even get it to clone without doing a Windows parallel install to do a regedit fix- fortunately I had a cloned image before running sysprep to restore to- but thats another issue), After cloning (using Acronis TrueImage and having sysprep'd the image) I went through the mini-setup and as soon as it booted into actual Windows the following error occurred: Windows SteadyState An unexpected error occurred (0x8004100c) When trying to run SteadyState I then received this error: Error You must be running a Genuine version of Windows to access Windows SteadyState. I then realized that my internet connection (wireless) had to be reset back up - as I had been using a wireless network connection and didn't Activate Windows during the mini-setup. I resetup the wireless connection, activated Windows, rebooted, no error, and I as able to run SteadyState. Just an FYI incase anyone else runs into the same issue.

Thanks for sharing the experience with us. It is true we have to activate and validate the windows during the mini setup wizard.

Hi there, i have the same problem after cloning. We don't use SysPrep because we haven't had any problems yet without it. The difference is that we use a volume license key for our PCs so they are "activated by default". :-) Is there anything elsei have to care about before cloning a machine with SteadyState?

For testing,we just uninstalled and reinstalled SteadyState. It worked just until the next restart. Then the error message comes again. We are now testing if there's a problem with any of the scripts, restrictions or start options by using procmon & regmon.

Hi FFM_Admin, Thanks for your sharing. If the error also mentioned You must be running a Genuine version of Windows to access Windows SteadyState Please check if the system has been activated when it starts. We can run the following command from Start, Run to test this: oobe/msoobe /a For your reference, its not recommended to lock a user profile or turn on WDP before creating a image. You can refer to the following threads: Do not lock a user profile before creating an image: http://forums.microsoft.com/WindowsToolsandUtilities/ShowPost.aspx?PostID=1984622&SiteID=69 Do not turn on WDP before creating an image: http://forums.microsoft.com/WindowsToolsandUtilities/ShowPost.aspx?PostID=1815384&SiteID=69 Best Regards,

Hi there, the system is properly activated. Neither a profile is locked nor WDP is turned on (we don't use locked profiles). The error is caused by the bubble.exe, which is apparently responsible for informing the user about actions WDP is going to perform. Deactivating the autostart option in msconfig or deleting the referring registry key does not solve the problem but removes the error message. ;-) We still didn't find out why the bubble.exe causes this problem. One reason may be a configuration problem on the client but we recognized that problem on several different PCs. By the way we found out, that the bubble.exe accesses several registry keys belonging to network options (like DNS parameters in the lanmanserver section) (--> RegMon). This may be interesting for further investigations.

Hi FFM_Admin, Thank you for your efforts on this issue. Before we go any further, I would like to confirm the error message as the circumstances can be different. I also would like to know how you cloned the system. In our local test, we did not encounter this issue. It should not be a designed behavior. Based on my research, the error code 0x8004100C means the following: WBEM_E_NOT_SUPPORTED 0x8004100C The feature or operation is not supported. As SteadyState stores some configuration information, such as WDP mode, in WMI, I suspect that this problem occurs because the SteadyState related WMI classes and objects are missing or corrupt. We can perform the following steps to troubleshooting this issue: Step 1: Uninstall and then reinstall SteadyState to test whether this issue continues. Step 2: As all WMI classes in SteadyState are used for WDP, lets turn on Windows Disk Protection (WDP) to check this issue ----------------- 1. Open SteadyState from an administrator account. 2. Click Protect the Hard Disk, click the check box before On. Click OK. 3. If the issue persists, we can turn off WDP to check if there is any change. Step 3: Check the connection of WMI repository ----------------- 1. Click Star -> Run, type wbemtest in the text box, and click OK. 2. Click Connect, type root\wmi in the text box, and click OK. Can you connect properly? 3. Click Enumerate Classes, check the Recursive option, and click OK. Is WDP_Control listed in the query result? If this issue persists, please provide me with a screenshot of the error and the dialog of Protect the Hard Disk. To capture screenshots, complete the following steps: ----------------- 1. Press the Print Screen key on the upper right corner of the keyboard when the error occurs. (The Print Screen key is to the right of the F12 key on the keyboard). 2. Open Paint from Start -> All Programs -> Accessories-> Paint. 3. Click Paste on the Edit menu in the Paint program. 4. Save it and send it to v-shshao@microsoft.com as an attachment (if it is possible, please save it as a *.gif or *.jpg file). Regards,

Hi, sorry for keeping you waiting! :-) I did another test: i just installed a new system just the way we do it everytime. Before configuring the system,I installed SteadyState and it did not show the error message. After that, I executed a batch file that configures several registry keys to optimize the system performance. After that, Steady State shows the error message. The possible range of registry configurations reaches from HKEY_LOCAL_MACHINE to HKEY_USERS_DEFAULTsection, because the error appears independently from the user being logged on. I just tried to find out which key could cause such an error, but I didn't succeed yet. Since the batch file is very long I do not post it here. I will send it to your email address shown in your last post! :-)

Thank you for your update on this issue. It seems the issue is closely related to the registry changes. By the way, please compress the batch file first to make sure it can be accepted by email system. Regards,

OK, it's on its way. By the way: another issue we are dealing with is a slow logon procedure since installing SteadyState. I will post thatunder the appropriate topic.

Same problem here after Sysprep and Norton Ghost 10.0 cloning.

Hi JHirschi, Would you please include more background information about this issue? As the cause can be different, I recommend submitting a new thread to avoid confusion. Regards,

I didn't open a new thread because I can't offer much information--only a summary: 1. Unlocked, removed all restrictions from, and then removed the public limited user accounts (because I haven't been able to clone them yet successfully with SteadyState). 2. Installed SteadyState. 3. Ran sysprep with Reseal and Quit (did not shut down). 4. Backed up computer with Norton Ghost 10.0. 5. Restored to target computer with identical hardware. 6. Ran through setup. 7. Activated Windows. There was no Start-->All Programs-->Accessories-->System Tools-->Activate Windows, so I ran "oobe/msoobe/a", and the response was that Windows was already activated. Curiously, I restored to 7 computers--only half of them had the problem, and the problem went away on the other half after a number of reboots for various things. Some kind of timing problem?

Is there any different between those computers? If they have identical hardware and software environment, is there any special operation to the computers which experienced the reactivation issue? FYI, if your organization licenses Windows XP through one of Microsoft's volume licensing agreement programs such as Open License and Select License, you will not be required to activate those Windows XP licenses. Thus, issue can also related to your license type. Regards,

Hello... I know this thread has some age on it, but I just wanted to share what resolved the problem in my case, as I didn't see this posted. For me, the error went away after EnableEvents was set to 1. (I didn't realize it was previously set to 0 in the registry on my system.) It's located in HKLM\Software\Microsoft\WBEM\CIMOM ... After being set to 1, Windows Disk Protection started at the next reboot. I figured I'd put this note here because when I searched for the error from a search engine, one of the 1st results was: http://social.microsoft.com/Forums/en-US/windowssteadystate/thread/507b19cb-7764-4f71-ba9f-af37a564b45b/ & that thread referred the poster to this one & another one. I ran into the error not due to cloning or anything like that but due to a tweak that was applied.

... EnableEvents was set to 1. (I didn't realize it was previously set to 0 in the registry on my system.) It's located in HKLM\Software\Microsoft\WBEM\CIMOM ... hat geholfen! Danke Vielmals