| Author |
 Topic  |
|
|
toonei
Welcome Newcomer
USA
6 Posts
Status: offline |
 Posted - 11/19/2011 : 02:33:48 AM
|
Trying to put steadier state together so I can use it. I have run the cvt2vhd command and it works perfect, when I run the prepnewpc command I get the following error message--
Version: 6.1.7600.16385
[ 99% ] Applying <with verification> progress
[ ERROR ] q:\Windows\winsxs\amd64_microsoft-windows-winpe-background_31bf3856ad364e35_6.1.7600.16385_none_d8b3fe4cd1e66081\winpe.bmp <Error = 577>
Error restoring image.
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
ERROR: ImageX failed with return code 2. Can't continue, exiting.
X:\>
I have re-downloaded the steadier state files and started from scratch building the ISO etc but am still getting the same error message.
Has anyone experienced this or have you got this to complete successfully? Any help or thoughts about what to do would be much appreciated.
|
|
|
Mark Minasi
Chief cook and bottle washer
USA
10658 Posts
Status: offline |
Posted - 11/19/2011 : 4:26:31 PM
|
It's got nothing to do with CVT2VHD, it's a problem imaging WinPE onto the target computer's hard disk. The key is error 577 and while I've never seen it, a bit of searching found these links:
http://reboot.pro/4446/
http://social.technet.microsoft.com/Forums/en/w7itproinstall/thread/f77a44f1-705a-427c-8f7d-5a95eb20ba6d (not helpful, but interesting to see that ImageX does this on some hardware).
Other thoughts:
-try deploying to a different computer in case it's a hardware issue.
-check for malware on the system you created buildpe on
-Double-check that you have the WAIK specified in the documentation. It's a download dated 5 August 2009.
-Check you're not trying to deploy a 64 bit image to a 32 bit system.
-Recreate the BUILDPE USB disk/CD and look at the error messages very closely to see that there wasn't an error shown while doing imagex /apply to the mounted USB stick/CD image. Remember the files in windows\logs\buildpe
Apologies that I don't have a more exact answer ... I just can't duplicate it so all I can do is look at what others have experienced. |
Mark
tweetin' at mminasi |
 |
|
|
toonei
Welcome Newcomer
USA
6 Posts
Status: offline |
Posted - 11/19/2011 : 5:22:29 PM
|
I will look into it further. Thanks for the reply.
I have tried this on 2 different computers, both of these are malware free, I loaded new images on the hard drives specifically for testing with the Steadier State program.
I ready a lot of machines for deployment using Paragon and SCCM so I am familiar with WAIK, x86-x64 bit systems.
I have also recreated the BUILDPE USB disk/cd several times.
I didn't see any errors after BUILDPE ran.
I will do as you suggest, redownload the WAIK again and start completely from scratch one more time. I will look at the logs.
The links were interesting but don't think it is hardware related with WINPE. I use these same boards and hardware at work to do a lot of imaging. We used to deploy images using Bart's PE, now are using Paragon and SCCM so I'm sure it isn't hardware related.
I will look closer at this and really appreciate the program and your help with this Mark.
Thanks for the input. |
|
|
|
Mark Minasi
Chief cook and bottle washer
USA
10658 Posts
Status: offline |
Posted - 11/20/2011 : 08:33:32 AM
|
I all just sounds so odd, Michael. Basically all I'm doing is
1) Having you download and install the WAIK, which includes a winpe.wim (as you probably know).
2) Run a batch file, buildpe, that just does a copype to create a standard WinPE workspace into %temp%\buildpe.
3) Buildpe then uses imagex to mount winpe.wim. The output from the imagex /mount is in imagexmount.txt in the log folder. In any case, if there's a return code from imagex that is nonzero, I throw an error and exit.
4) Once mounted, I create a folder \SDRSTATE in the root of winpe.wim and copy the batch files into it. Then some other batch files -- cvt2cmd, startnethd, and prepnewpc -- go into the root of the Winpe image. A copy of imagex.exe goes into System32. I then add some commands to the existing startnet.cmd.
5) Then ImageX unmounts. Again, I check for a zero return code. The results are in imagexunmount.txt in the log file. If the signatures could not be rewritten for some unknown reason, I assume ImageX would fail at that point. (No way to simulate it to see.)
6) With a properly created winpe.wim built, move it to iso\sources, as usual. The output of that command appears in startlog.txt in the log folder but, again, if that weren't there, you wouldn't be able to even boot the USB stick/CD.
Following that, when you run prepnewpc this is the only ImageX command executed:
imagex /apply %realdrive%\sources\boot.wim 1 %tdrive% /check /verify
Which is pretty much a textbook lay-down-WinPE situation. Try removing the /check from the line, perhaps that'll help, although if it does I'll still be puzzled.
I'll be interested to see what you get when you re-download the WAIK. Microsoft has messed with that thing a few times and screwed it up, only to silently replace it on microsoft.com/downloads, although it's been a while since they did that.
I agree about the links, but they were all I could find. Thanks again.
|
Mark
tweetin' at mminasi |
|
|
|
toonei
Welcome Newcomer
USA
6 Posts
Status: offline |
Posted - 11/29/2011 : 12:34:18 AM
|
A real head scratcher Mark. I completely started from scratch, downloaded new SS zip file, WAIK, created new SDRSTATE folder on the root of C:, extracted the SS zip file into, installed WAIK, ran BuildPE, created a new USB boot disk, ran cvt2vhd and saved it to an external Sata USB drive, so far so good.
Shutdown the computer installed a new hard drive to copy the image.vhd file to. Ran prepnewpc and still got the same error message I have been getting.
Think I will grab a new motherboard, processor, memory etc. from work and try again, just don't know what else to try, I don't like an inanimate object getting the better of me.
Will keep you informed.
|
|
|
|
larsrohr
Welcome Newcomer
USA
2 Posts
Status: offline |
Posted - 11/30/2011 : 5:42:46 PM
|
Thanks, toonei, for bringing this up. I just ran into this myself, and found this forum topic while googling it.
For background, I'm using 64-bit Win7 Ent, and the vhd image was created from the same laptop that I want to deploy to: a Lenovo T61p
I was able to get prepnewpc working, though -- removing the /check option didn't help, but removing /verify did. Now my T61p is successfully set up and working with Steadier State, and I'm very happy. I plan to use this with a small stash of laptops available for loan within our department. |
|
|
|
toonei
Welcome Newcomer
USA
6 Posts
Status: offline |
Posted - 12/01/2011 : 02:12:45 AM
|
Larsrohr
Thanks for your input, after re-reading Marks reply about the /check option I did try removing the /check option and got the same results you did. I will try removing the /verify option, hopefully it works, I will reply back with the results. Thanks again.. Glad you got it working. How is it? |
|
|
|
larsrohr
Welcome Newcomer
USA
2 Posts
Status: offline |
Posted - 12/01/2011 : 6:37:04 PM
|
It's working great.
I've gone through a merge procedure once, and a rollback once, and both worked flawlessly.
|
|
|
|
toonei
Welcome Newcomer
USA
6 Posts
Status: offline |
Posted - 12/02/2011 : 12:37:53 AM
|
| That's good news. I'm going to try it again on a new system tomorrow night. Will let you know how it goes. |
|
|
|
toonei
Welcome Newcomer
USA
6 Posts
Status: offline |
Posted - 12/05/2011 : 02:06:59 AM
|
Success...removing the /verify switch did the trick for me also. Have it working and am very pleased.
My thanks to you Mark for developing this and the words of wisdom and to you also larsrohr for your input. |
|
|
|
Mark Minasi
Chief cook and bottle washer
USA
10658 Posts
Status: offline |
Posted - 01/02/2012 : 4:37:50 PM
|
| Thanks, guys! |
Mark
tweetin' at mminasi |
|
|
|
Pesos
Honorable But Hopeless Addict
USA
3506 Posts
Status: offline |
Posted - 04/22/2012 : 6:16:02 PM
|
| Finally getting around to trying SS, and I ran into this problem as well trying to deploy to a Dell Inspiron 600m laptop. I typed in the imagex command manually omitting "/verify" and that worked fine for me too. |
-Wes |
|
|
|
greeboid
Welcome Newcomer
United Kingdom
1 Posts
Status: offline |
Posted - 01/09/2013 : 06:18:52 AM
|
I also experienced these problems and tried removing the both the /check and /verify switches and, frustratingly, it still didn't work.
So I looked at the error that was flagged up and it was:
[ 99% ] Applying <with verification> progress
[ ERROR ] q:\Windows\winsxs\x86_microsoft-windows-winpe-background_31bf3856ad364e35_6.1.7600.16385_none_d8b3fe4cd1e66081\winpe.bmp <Error = 577>
This made me wonder about the actual bitmap so I took a look at the properties of the file within the SdrState folder from which the USB boot stick and/or DVD is created.
I saw that on the General Tab there was a message:
Security: This file came from another computer and might be blocked to help protect this computer.
There was a button labelled: Unblock
So I did, on both bitmap files.
I then wiped my USB key by running Buildpe again and now prepnewpc ran successfully WITH both switches.
The only issue I then had was that the robocopy didn't work for me, probably due to where and how my image files were stored, so I just xcopied them.
All working now... just testing my StedierState computer and looking into tweaking stuff before deploying to about 20 machines.
Hope this is helpful to anyone who has had similar issues.
|
|
|
|
Leeham
Welcome Newcomer
United Kingdom
4 Posts
Status: offline |
Posted - 01/09/2013 : 07:00:32 AM
|
Hi all,
I ran into the same error as toonei. I edited the c:\sdrstate\prepnewpc.cmd and removed the /verify as discussed. Rebuilt the Bootable USB stick and then ran prepnewpc on my test PC. Works fine now.
I'll also try greeboids suggestion which I've only just seen.
|
|
|
|
Mark Minasi
Chief cook and bottle washer
USA
10658 Posts
Status: offline |
Posted - 01/11/2013 : 3:21:54 PM
|
Interesting -- so the BMPs somehow got a "this came from the internet" alternate stream.
Thanks for the info! |
Mark
tweetin' at mminasi |
|
|
|
dugjones
Welcome Newcomer
1 Posts
Status: offline |
Posted - 05/02/2013 : 11:07:33 AM
|
I had this same issue and looked so mounted the boot.wim located in the sources folder of the thumb drive. I navigated to the folder mentioned above and the winpe.bmp was there but was only 26kb in size. I replaced this file with a modified winpe.bmp and committed the changes and everything worked fine.
I rebuilt the thumb drive using modified winpe.bmp and winpe1.bmp files and it worked great. I did not have to modify the scripts at all. Hope this makes sense and helps someone. |
|
|
| |
Topic |
|
prepnewpc
