Ghost Solution Suite

I have installed GSS 2.5 on my Windows 7 Professional (English with Slovak regional settings). After that I have downloaded and installed all updates thru LiveUpdate. Update to 2.5.1 had to be installed manually (downloaded by LU, then unrar from cache and run setup.exe), because it failed when installation started by LU. Now there are no updates found by LU.

Now I try to create bootable USB key with Win PE by Ghost Boot Wizard. Process always fails with error "WIM file for this configuration of Windows PE is invalid."

I have also tried to rollback win files, no success. http://www.symantec.com/connect/blogs/rollback-corrupt-winpe

Btw., where can I get installation files for GBW with 2.5.1 upgrade integrated?

Thanks,

MaFe

Hi,

You could get the latest version (2.5.1) from https://fileconnect.symantec.com. This would require you to have the serial number and only then you could download it.

Hope this helps !

I have downloaded GSS 2.5.1 from fileconnect, uninstalled GSS from my notebook, deleted all files under program files\symantec, deleted all files under users\all users\application data\symantec and installed GSS 2.5.1 from downloaded zip file.

When I run Ghost Boot Wizard, it stops at the same place with same error...

Somewhere on the net I have found a note that GBW has problem with Slovak Windows 7. I am running an English version of Windows 7 Pro, however my locale is Slovak.

What is wrong?

Hi,

I have seen that even after performing clean uninstall, people get the same corruption issue back. This can be due to ghost registry files.  I would appreciate If you can try installing GSS2.5.1 in another machine rather than trying on the same.  I am pretty sure that this will work fine.


Regards,
Dilip Sebastian



---------------------------------------------------------------------------------
If your issue gets fixed with this, Mark the same as solution

Hi,

This could be a possible registry entry that needs to be removed as Dilip has stated. The option would be is to try Ghost with another machine if you don't want to play with the registry.

Hope this helps !

I have tried it on my collegue's notebook, works fine.

What should I remove from registry? I have no problem to uninstall GSS, clean registry entries and install it again.

Hi, Please make use of the following web document to perform manual uninstall of GSS.
http://service1.symantec.com/support/on-technology.nsf/854fa02b4f5013678825731a007d06af/0f528a897ced68ac882576b6007429dc?OpenDocument


See whether this works.



Regards,
Dilip Sebastian



------------------------------------------------------------------------
Mark as solution if this helps to fix your issue

Dilip,

thanks a lot for tip. I have uninstalled GSS 2.5.1 from my notebook and investigated a bit what remained in the registry. In my case uninstall has removed all installation information, so I did not apply solution from support case you have recommended.

However I have found that there is a key in registry HKEY_CURRENT_USER\Software\Symantec\Symantec Ghost\Ghost Boot Wizard\WinpeLastLocation which points to location of WinPE. In my case this key pointed to disk F: where I had GSS 2.5 installed some time ago. This key was not removed during GSS 2.5 uninstall, nor during GSS 2.5.1 install/uninstall. So I have removed it and installed GSS 2.5.1. Now it works!

I don't have disk F: attached to my notebook anymore. When I have applied solution from http://www.symantec.com/connect/blogs/rollback-corrupt-winpe, GSS has used file copied to C:\Users\All Users\Symantec\Ghost\Template\common\winpe\sources in order to recreate boot.wim in winpe\sources and winpe-512\sources during GSS start, however looked for wim files in disk f: during ghost CD image creation, and because disk f: was not present, displayed an error.

MaFe

Thanks for this.  I was having this error after a fresh install of GSS 2.5.1 on a win7 64bit box, with no previous install of gss before.  I went into HKEY_CURRENT_USER\Software\Symantec\Symantec Ghost\ and deleted the entire Ghost Boot Wizard Key.  Restarted ghost boot wizard, and voila, now I can make ISO!