Disk image create and restore issue

I need a solution

Hello, I have a Windows Server 2012 R2 server with GSS 3.3 installed. Client computer OS is Windows 10, Disk Management looks like attached image “disk_management.png”. In diskpart concole the disk and partition information looks like attached image “diskpart.png”
In GSS console:
Create image job command: -CLONE,MODE=CREATE,SRC=2,DST=%IMAGE_FILENAME% -SURE -SPLIT=0 -Z3
Image location: 1:2ImagesImage.gho
Restore image command: -CLONE,MODE=RESTORE,SRC=%IMAGE_FILENAME%,DST=2 -sure
Image location: 1:2ImagesImage.gho

1. To create image, if image location set to D:Imagesimage.gho, the job seems never complete, status is keeping “Uploading disk image…” unless I delete the job manually. If image location set to 1:2xxxx.gho, the job completed successfully. Why this happens?
2. Restore image not work with above ghost command, the warning message is “The Drive number selected for deploying an image connot be same as the Drive number on which the image is stored.” Anything wrong in the restore command? Please advise.



Ghost disk numbering

I do not need a solution (just sharing information)

Ghost and gdisk both use one-based indexing for disk numbers.

Diskpart and some other disk tools use zero-based indexing corresponding to the “physicaldisk” numbering Windows uses. For instance, Disk 0 in diskpart is “\.PHYSICALDISK0” (deviceID used by Windows). 

I need a way to tie the disk numbering in gdisk to diskpart programmatically. Can I simply increment the disk number used by Windows to get the Ghost/Gdisk number? Does Ghost used a different method to enumerate the HW?

Diskpart can give me the geographic location of a disk in the system (select disk #, detail disk). My system can change the number and type of disks, but they can be identical models, so the location is one of the only ways to identify a target disk. Does Ghost/gdisk provide any similar options?




Computer stuck at “bootguard”

I need a solution

Upon startup, one Win7 computer just gets stuck at the black screen with “bootguard _” on it. I’ve looked at several solutions online and so far none of them work. I do have a WinPE UFD with the encryption stuff on it, but any WinPE environment won’t even recognize there’s an internal hard drive at all. I can boot up with a GParted live CD and that will see the disk just fine. I can even browse its contents with the GParted live CD (between that and the SEE snap-in), so I know the disk is not encrypted.

I’ve tried using diskpart, but of course, the internal HDD is not recognized as even being connected by the Windows PE environment
I’ve tried using Bootrec.exe /FixMbr, but of course, the internal HDD is not…. you get the picture. Anything I’ve tried won’t work without the WinPE environment realizing that there’s a disk attached. Only live linux distros see the internal HDD.

Any suggestions would be greatly appreciated. Thanks!



How To Resize Citrix PVS vDIsk Using DiskPart Utility


  • If you have subversions or differential disks of the PVS disk, merge it to an base disk. Delete the merged version from the PVS console.
  • And also before performing any activity please backup the old VHD or vDisk, in case of corruption on disk same can be used.
  • The commands in this post must be run while the VHD file is closed not be in used. It cannot be attached with disk manager and it cannot be attached to a running VM.

1. Change vdisk to private mode.

2 Use inbuilt diskpart Utility to resize vdisk in any Windows Machine


3. Open Comand Prompt or Powershell and get Diskpart

On Diskpart enter “Select vDisk file=”


4. Enter “List vDisk”to check if the vDisk has been added or not.


5. After that Expand the vDisk by using following query “expand vDisk maximum=XXX (in Mb)”. The size should be in “MB”


6. On Diskpart enter “attach vDisk” to attach it. Type “list disk” to check if the vDisk has been attached.


7. Type “List Volume” to see what are the available volumes


8. Type “Select Volume 3” the vDisk which you want to resize and enter “Extend” to extend the vDisk.

Note: The number of the vDisk you want to resize.


9. Now the vDisk has been extended to verify type “List Volume” to see the status. after checking the status. Type “Detach” to detach the vDisk.




  • No Related Posts

Ghost not deploying image but no logs

I need a solution

I have a decent number of machiens that ghost seems to fail at but it is not creating the ghost error logs in PE.

This is the error shown in the console

ErrorMessage: Exception has occured in File Tcube_ClientImageDeploy.cpp at Line No 978. Type of exception is ClientImageDeployException. Error Description is Child Process returned an error. The exit code from process is 3. Value of Windows error code = 183 and message is Cannot create a file when that file already exists.

I have tried gdisk64 to delete partitions in case its somethign with that and that gives me the error regardless of what gdisk64 parameter I try

gdisk64 (W) fixed disk has partitions) that extend past the end of the disk

I have also tried diskpart and get errors there too.  I know we can’t all of a sudden have 100 drive failures, so any help is appreciated as they do pass the internal computer drive tests.



Laptop freezes at pre boot screen

I need a solution

After installing SEE on a laptop it now cannot get past the pre boot screen. The user paused encryption at about 85% yesterday and then locked Windows and shut the lid. When booting up the morning after the laptop gets to the SEE ‘press any key to continue’ screen but no buttons on the keyboard elicit any response, even with a USB keyboard plugged in. Caps lock + Scroll lock are responsive on the keyboard at POST but as soon as it gets into the Symantec Encryption screen it becomes unresponsive. 

When booting to the customised Windows PE disk and trying to decrypt the disk it states the disk is not encrpyted or the encryption record might be damaged. ‘Diskpart list disk’ shows no fixed disks. 

How can we get this laptop booted in to Windows or decrypt the drive? 



Failed to mount Elastic Layers, “A virtual disk support provider for the specified file was not found.”

There may be multiple causes for this. The error really just means that Windows is being blocked by policy from allowing the disk to be attached. One identified cause is a specific GPO:

Computer Configuration/Administrative Templates/System/Device Installation/Device Installation Restrictions – Prevent installation of devices not described by other policy settings.

If you disable that setting, you should be able to mount the VHD manually using DiskMgmt or DiskPart, and Elastic Layers should start attaching properly at logon. Be careful, of course, to find where that GPO is set. If it’s in your domain policies, then the setting might be captured in the Platform Layer, and not get cleared by the updated GPO before a user logs in.


LONG Load Times, Scripted Install an Alternative?

I need a solution

This is a multi-part question, I’m looking for some guidance. 

I manage a 30 PC computer lab for a department at a college. We configure the image, sysprep it, the deploy it. With Windows 10 however, that produces insanely long load times. Some students report waiting up to 5 minutes to log in. Log offs can also take 5-10 minutes. 

I’ve taken steps such as keeping the number of programs in the base image to a minimum and installing everything afterwards with scripts, I’ve also removed all of the Windows store apps and our group policy campus wide disables the windows store. 

Still, I can’t get the load time for a login to under 1 minute. Best I can get is 1 to 1.5 minutes. 

Our desktop computers use SCCM OSD to install instead of block imaging. So I decided to explore Ghost’s scripted install since we can’t use the OSD for labs. So here are some questions:

1.) Is there anything I might have missed that you could suggest to improve load speeds?

2.) When doing the scripted imaging, the partitioning part confuses me. All of the drives are NTFS formatted SSDs. Do I need a custom script or can I use diskpart? If I need a custom script, are there any resources on what that would look like? 

I appreciate any tips or guidance. I got away from imaging for a few years and now I feel like I forgot everything. 



Re: Formatting a disk in Hyper-V is slow

Yup, that’s what I’m doing. But even a quick format is slooooow. And I’m seeing it on LUNs presented by VNX, Unity, Unity AFA, XtremIO. Quick Formatting (in diskpart) is always slow. It is slightly faster on all flash arrays, but it’s still slow. On average it takes up to 15 minutes for a 2TB LUN, but like in my question, the 9TB LUN took much longer.


Windows 10 Servicing – OSD upgrades and OS servicing

I need a solution


Is there a solution for doing zero touch OSD upgrades from Windows 7 to Windows 10 on SEE encrypted drives? Is there a solution for servicing the OS for encrypted drives?

Decryption is not an option unfortunately, and most of my automation attempts for a zero touch upgrade have been thwarted by the fact that I can’t write the boot wim to the drive for WinPE.

Right now the only thing that works is a diskpart, cleaning the drive, repartitioning and starting the task sequence from boot media. If there is no option, is it documented somewhere so that I can share this with my team?