Quantcast
Channel: Symantec Connect - Ghost Solution Suite - Discussions
Viewing all articles
Browse latest Browse all 1315

GSS 3.1 failed to create correct Windows 7 bootloader entries

$
0
0
I do not need a solution (just sharing information)

Hello,

I have been stuck for a couple of days with my Windows 7 stations not been able to enter the Symantec Deployment Solution Preboot Environment created from a WinPE 10 x64 automation folder.

The next boot invariably failed with error 0x0c000000f.

Odd enough, the same things does not happen on windows 10 clients.

After reviewing both Windows 10 and Windows 7 bootloaders, there are visible differences.

Here is a Windows 10 bootloader, as seen after the automated folder is installed. This one work as expected :

Bootloader 10.png

Here is a Windows 7 bootloader, as seen after the automated folder is installed. This one doesn't work:

Bootloader 7.png

The ramdisk pointer for both "device" and "osdevice" are the only differences beetween the 2 bootloaders.

This only way to make it work is to manually edit the bootloader and change "ramdisk=[boot]" to "ramdisk=[C:]"

The Symantec Deployment Solution preboot Environment work properly after doing this modification.

Can you reproduce this "bug" ?

0

Viewing all articles
Browse latest Browse all 1315

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>