WINDOWS 7 WILL NOT BOOT AFTER DEPLOY
-
Thanks in advance everyone !!!
i have been using for for years and had no issues with XP, however 7 is driving me crazy.
I had try both SINGLE DISK(NTFS ONLY, RESIEZABLE) and MULTIPLE PARTITION IMAGE - SINGLE DISK (NOT RESIZABLE). I am able to upload the image to the FOG server ( Release 1.1.2 ) on a Ubuntu Desktop 64 bit with no problem from a GIGABYTE GA-H61M-S2PV but after a deploy the image to another PC with the same board, windows will simply wont boot.
What have i done to sysprep the image before uploading
1.- upload the image right after installing, updating and installing drivers ( no sysprep, nothing )
2.-
[SIZE=4][B][FONT=sans-serif][SIZE=17px][COLOR=#000000]Windows Vista and Windows 7[/COLOR][/SIZE][/FONT][/B][/SIZE][FONT=sans-serif][COLOR=#000000]Right before uploading the image the MountedDevices registry key must be cleared. If it is not, the master image and subsequent deploys will result in this problem: [URL=‘http://www.fogproject.org/wiki/index.php/Vista_Image_says_0xc000000e_\windows\system32\winload.exe_can_not_be_loaded’][COLOR=#5a3696]Vista Image says 0xc000000e \windows\system32\winload.exe can not be loaded[/COLOR][/URL][/COLOR][/FONT]
[FONT=sans-serif][COLOR=#000000]This can be accomplished by [I]any [U]one[/U][/I] of the following methods:[/COLOR][/FONT]
[LIST=1]
[]use Sysprep with the /generalize switch
[]run [URL=‘http://www.fogproject.org/wiki/index.php?title=FOGprep&action=edit&redlink=1’][COLOR=#a55858]FOGprep[/COLOR][/URL].exe ( I HEARD THIS IS NOT NEEDED ANYMORE, DIDN’T RUN IT)
[]manually delete the [FONT=monospace]??\volume{…}[/FONT] keys in the registry under “HKLM\SYSTEM\MountedDevices”
[]run the following from an administrator’s console:
[/LIST]
[COLOR=#000000][FONT=monospace]bcdedit /set {bootmgr} device boot
bcdedit /set {default} device boot
bcdedit /set {default} osdevice boot[/FONT][/COLOR]still No luck !!!
Please correct me if am wrong, i know that at some point i have to create an unattended.xml file for better deployment, but i at least want to make sure that i can deploy images.
What am i missing ?
Do i have to do something to the bios ( UFEI ) ?again very much appreciated.
-
it sounds like you created one image before doing any prep-work to the image, and created another after.
does it work if you try to deploy the one made before you modified windows? -
Hi thnks Junkhacker
Nop, just to try ( first run with 1.1.2) i uploaded the image from right after installing updates and drivers. Then i deployed the image which complete with no errors but windows itself will not boot.
Then i thought, maybe i do need to run sysprep at least but still after deploying windows will not boot !!!
-
Can you try redoing the upload of the image.
But create an upload - debug task, rather than a normal upload task.
Before uploading, you’ll be brought to a “terminal” prompt.
Run the command:
[code]gdisk -l /dev/sda[/code] What’s the output? -
thanks a lot Tom…
Am on it. I’ll let you know once done.
-
Here it is !!!
[ATTACH=full]1133[/ATTACH][ATTACH=full]1134[/ATTACH]
[url=“/_imported_xf_attachments/1/1133_IMAG0068.jpg?:”]IMAG0068.jpg[/url][url=“/_imported_xf_attachments/1/1134_IMAG0070.jpg?:”]IMAG0070.jpg[/url]
-
okay you can cancel the task and reboot that system.
On the system you’re attempting to “download” the image, can you do a “download-debug” and run the same command?
-
Yes Sir,
Will do !!!
-
download-debug !!![ATTACH=full]1135[/ATTACH][ATTACH=full]1136[/ATTACH]
[url=“/_imported_xf_attachments/1/1135_IMAG0071.jpg?:”]IMAG0071.jpg[/url][url=“/_imported_xf_attachments/1/1136_IMAG0072.jpg?:”]IMAG0072.jpg[/url]
-
i believe that at this point, tom would ask you to enter the command “fog” and report on if the download succeeds.
-
Now run fog
-
it did run, i will send you guys pics ones done so that you can see that windows just won’t boot…
it does create the 100 MB Windows reserved partition
and is creating the actual windows installation partition. -
yeap didn’t work
[ATTACH=full]1143[/ATTACH][ATTACH=full]1144[/ATTACH][ATTACH=full]1145[/ATTACH][ATTACH=full]1146[/ATTACH][ATTACH=full]1147[/ATTACH][ATTACH=full]1148[/ATTACH]
[url=“/_imported_xf_attachments/1/1143_IMAG0073.jpg?:”]IMAG0073.jpg[/url][url=“/_imported_xf_attachments/1/1144_IMAG0074.jpg?:”]IMAG0074.jpg[/url][url=“/_imported_xf_attachments/1/1145_IMAG0075.jpg?:”]IMAG0075.jpg[/url][url=“/_imported_xf_attachments/1/1146_IMAG0076.jpg?:”]IMAG0076.jpg[/url][url=“/_imported_xf_attachments/1/1147_IMAG0077.jpg?:”]IMAG0077.jpg[/url][url=“/_imported_xf_attachments/1/1148_IMAG0078.jpg?:”]IMAG0078.jpg[/url]
-
you mentioned UEFI, was that enabled in the bios when the system was working, before you pulled an image from it?
-
What happens if you tell it to run normally
-
[SIZE=12px]Junkhacker[/SIZE]
[SIZE=12px]UEFI was enable in the bios on my source computer, i did the whole installation with the UEFI enable.[/SIZE]
[SIZE=12px]Tom[/SIZE]
[SIZE=12px]It does the same thing windows will not boot, with the commands you guys gave me i was able just to see it step by step but same result.[/SIZE]
[SIZE=12px]To be quit hones and again you guys are the experts but i think it has something to do with :[/SIZE]
[SIZE=12px]* UEFI which i don’t fully understand but i think i read it on a different post.[/SIZE]
[SIZE=12px]* GPT and MBR [/SIZE][SIZE=12px]just to try i am going to disable UEFI and re-install windows completely on a third computer ( same hardware )[/SIZE]
-
Based on the pictures you provided your systems are not booting in Uefi mode because uefi enforces GPT partitions your partitions do not have any GPT set up
-
Your issues appear to me to be more likely related to AVG or some form of antivirus has a driver installed that’s unsigned
-
i just did :
- full windows 64 b pro
- windows updates
- motherboard drivers
No additional software !!!
-
Can you create a separate image but without the
[quote=“AlonsoP, post: 32599, member: 24925”]1.- upload the image right after installing, updating and installing drivers ( no sysprep, nothing )[LIST=1]
[]use Sysprep with the /generalize switch
[]manually delete the [FONT=monospace]??\volume{…}[/FONT] keys in the registry under “HKLM\SYSTEM\MountedDevices”
[*]run the following from an administrator’s console:
[/LIST]
[COLOR=#000000][FONT=monospace]bcdedit /set {bootmgr} device boot[/FONT][/COLOR][FONT=monospace]bcdedit /set {default} device boot[/FONT]
[FONT=monospace]bcdedit /set {default} osdevice boot[/FONT][/quote]BCD commands or registry key edit? My suspicion is it can’t find the device because it’s been removed. Normally BCD will attempt to find it (when it’s generalized) but I’m starting to think the removal of the MountedDevices is part of the problem. it has no idea where to look for the drives. It knows the boot system exists, and probably even knows the location of the “data” partition, but because it doesn’t know about the mounted devices, it fails thinking the device doesn’t exist.
