VHD disk compact

Hi,
I have installed Hyper V 2008R2 server. I have created a two VM. The Type of disk of both vm is .VHD.
My question is: VHD is unable to compact white spaces automatically from the disk and it could not reduce the vhd size after deletion the data. Is there any solution for it .
Can .VHDX type disk can help me to reduce the white space automatically?
IS there any way or method to compact the vhd without down the VM
Please suggest me the solution to over come this monthly disk compact activity on my vms to reclaim the host disk space
Thanks

Hi Sr,
Please try to defrag in VM first then shutdown VM and try to use "edit disk.." in hyper-v manager to compact the VHD file .
Benefit of VHDX file please refer to the link below :
http://technet.microsoft.com/en-us/library/hh831446.aspx
If you have any further question please fell free to let us know .
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Extract vhd / disk from image?

Is there a way to extract the os / data disks from an azure image so it can be mounted as regular disks on another azure vm?
For example, I capture an image of a vm. Later, I want to extract an earlier version of a file that exists on a disk in that image. Right now, I would create a new vm from that image, detach the data disk, delete the new vm, attach the data disk to another
vm, and finally access the file. Is there a way to re-create the disks stored in the image without going through the vm-creation bit?
As mentioned above, for data disks, I can detach it from a vm and attach it to another vm. But is there a way to do the same with the os disk? When I delete a vm and tell it to keep the attached disk, it doesn't seem to apply for the os disk. Or at least
I don't know where to look for it. For example, I take an image of a vm. Later the vm no longer boots. Instead of deleting the vm and creating a new vm from image, a less drastic approach is to shutdown the vm, detach the os disk, attach the os disk from
the image, and try booting the vm. Is this possible? I would normally do this on a <cough> competitor's cloud service.

It looks like every time I capture an image of a vm, a snapshot is taken of each disk and then a vhd object is also created. So can I convert the vhd's to a disk without going through the create-a-vm-from-image process? Going even further, if I just took
snapshots of my vm's, can I turn those snapshots directly into disks?

[VHD] Expandable VHDX Disk Remains Expanded and Cannot Be Compacted

Hello,
I've noticed that one of my VHDX virtual disks storing Windows Server 2008 R2 and attached to a virtual machine remains expanded and consumes maximum space assigned on creation even when this virtual machine is turned off.
The diskpart confirms disk is expandable:
Notice, the VDisk 1 pointing to the win2008r2dc.vhdx file is expandable.
However, looking at the disk size in Windows Explorer shows that the disk remains expanded to its maximum capacity even though it's not in use (I've detached the disk before viewing the disk files in Windows Explorer):
The disk highlighted in blue allocates all 100 Gbytes! You may see here that there's another one 100 Gbyte VHD disk (not VHDX one) --- the win8rp.vhd storing Windows 8 Release Preview, which is also used in a virtual machine,--- is allocated to roughly
67 Gbytes although it's an expandable virtual hard disk drive with a limit of 100 Gbyte.
Why does the win2008r2dc.vhdx allocate all its size and does not collapse to its actual size? I've checked the drive with scandisk and it does not show any errors.
Thank you.
Well this is the world we live in And these are the hands we're given...

Hello,
I've noticed that one of my VHDX virtual disks storing Windows Server 2008 R2 and attached to a virtual machine remains expanded and consumes maximum space assigned on creation even when this virtual machine is turned off.
The diskpart confirms disk is expandable:
Notice, the VDisk 1 pointing to the win2008r2dc.vhdx file is expandable.
However, looking at the disk size in Windows Explorer shows that the disk remains expanded to its maximum capacity even though it's not in use (I've detached the disk before viewing the disk files in Windows Explorer):
The disk highlighted in blue allocates all 100 Gbytes! You may see here that there's another one 100 Gbyte VHD disk (not VHDX one) --- the win8rp.vhd storing Windows 8 Release Preview, which is also used in a virtual machine,--- is allocated to roughly
67 Gbytes although it's an expandable virtual hard disk drive with a limit of 100 Gbyte.
Why does the win2008r2dc.vhdx allocate all its size and does not collapse to its actual size? I've checked the drive with scandisk and it does not show any errors.
Thank you.
Well this is the world we live in And these are the hands we're given...
I found that large VHDX files (64TB allocated) will grow but I use smaller ones for VDI VMs.
if you need to run with lots of VHDX files, you are advised to get lots of storage, lots of it
low cost NAS boxes are one suggestion
Corsair Carbide 300R with window
Corsair TX850V2 70A@12V
Asus M5A99FX PRO R2.0 CFX/SLI
AMD Phenom II 965 C3 Black Edition @ 4.0 GHz
G.SKILL RipjawsX DDR3-2133 8 GB
EVGA GTX 6600 Ti FTW Signature 2(Gk104 Kepler)
Asus PA238QR IPS LED HDMI DP 1080p
ST2000DM001 & Windows 8.1 Enterprise x64
Microsoft Wireless Desktop 2000
Wacom Bamboo CHT470M
Place your rig specifics into your signature like I have, makes it 100x easier to understand!
Hardcore Games Legendary is the Only Way to Play!

VHD Size Backup?

I have a question for DPM server. If there is a dynamic disk 600 GB or Fixed 600 gb, and It has got 300 gb data on it.
how does dpm backs it up? Does it back up full size of the VHD or only the data 300 Gb. on our DPM I can see something strange and it backs up the full VHD size, but wanted to re-check on it.
Thanks,

HI,
Lets take these separately, because behavior will be different.
1) Dynamically expanding VHD
a. When you created the .vhd it was logically 600GB, but physically only was only 1MB in size as no data has been written to it yet.
b. You use DPM to protect the VM containing the .vhd and DPM brings over the 1MB .vhd file.
c. In one day 300GB is written to the .VHD, the logical size is still 600GB, but the physical size has now grown to 300GB.
d. DPM backup will now be protecting a 300GB .vhd file and will bring over those changes and apply them to the .vhd on the DPM replica.
e. As time goes on you eventually get close to filling the .VHD with more data and the .VHD grows to 599GB.
f. DPM again will be protecting the whole .VHD and will bring over those new blocks (299gb) and apply them to the .vhd on the replica, new size is is now 599GB.
g. If you now delete 300GB of data on the .VHD, there will only be 299gb worth af actual files, but the .VHD never shrinks. DPM will delete the same 300GB worth of files on the REPLICA but .vhd is still 599GB.
h. If you want to shrink the .vhd, you need to run a disk defrag inside the VM, then a compact in Hyper-v. Once the .vhd is compacted, it's new physical size will be smaller - lets say 400GB
g. DPM will see that the .vhd is now smaller and will apply the same changes on the DPM replica., so now the .VHD is 400GB
Fixed Size VHD.
a. When you created the .vhd it was logically 600GB, and physically 600GB in size.
b. You use DPM to protect the VM containing the .vhd and DPM brings over the entire 600GB .vhd file.
c. In one day 300GB is written to the .VHD, the logical size and physical size is still 600GB.
d. DPM backup will bring over those changes and apply them to the DPM replica which is also 600GB in fixed size.
e. As time goes on you eventually get close to filling the .VHD with more data.
f. DPM again will be protecting the whole .VHD and will bring over those new blocks (299gb) and apply them to the replica and the .vhd is still 600GB fixed size.
g. If you now delete 300GB of data on the .VHD, there will only be 299gb worth af actual files, but the fixed size.VHD never shrinks. DPM will delete the same 300GB worth of files on the .VHD in the REPLICA, but .VHD remais at 600GB fixed size..
DPM Tape backups.
DPM will always backup the entire physical size of the .VHD files. In the case of fixed size .VHD's that will remain a constant (600GB in this case) for dynamically expanding, the size of the .VHD may vary as data is written or a defrag and compact
is performed.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Vdisk gets converted to type fixed from expandable during installation to native VHD...

I've tried everyway to Sunday to get work-arounds for this but I'm stumped...
I am breaking into the Windows 8.1 with Update installation after adding my license, and creating a setup to use Native VHD to install to.
I create a vdisk type=expandable, yet at some point during the installation it is getting converted to fixed!
I've tried everything I could think of including formatting it while in the CLI prior to refreshing the volumes, and selecting the VHD disk volume for installation. Yet, after the installation is complete... the "actual" vdisk file should
only be around 11-14GB (regardless of the maximum size during its' creation with diskpart), however... sure enough, after Windows has finished doing its' thing and rebooting... the file ends up being the same size as the maximum property provided during the
vdisk creation with diskpart.... it should not be, it was of type "expandable" >.<
Why is this happening?

Hi,
It's not possible that without any settings, it converts into fixed disk. So how did you configure?
Please follow this guide to check if you have operated that:
Converting to a fixed virtual hard disk–the easy way
http://blogs.msdn.com/b/virtual_pc_guy/archive/2011/12/28/converting-to-a-fixed-virtual-hard-disk-the-easy-way.aspx
Hyper-V Virtual Hard Disk (VHD) Operations Explained
http://blogs.technet.com/b/yungchou/archive/2013/01/23/hyper-v-virtual-hard-disk-vhd-operations-explained.aspx
In addition, compacting is not usefull with fixed disks.
Karen Hu
TechNet Community Support

Upgrading Windows 8 to 8.1 [Native VHD Boot]

Hey folks,
I've got Windows 8 RTM running in a native VHD on my Dell Latitude E6430. I just tried to initiate the upgrade to Windows 8.1 by extracting the Windows 8.1 ISO with 7-Zip, and launching setup.exe from the extracted folder. Unfortunately, when I tried to
initiate the upgrade, I got an error message saying "You can't install Windows on a virtual drive." Does anyone know what this means?
Obviously, I already have Windows 8 running in a native VHD, so I would expect to be able to perform an upgrade of the operating system, just as if it were installed directly onto a physical partition. Is it only possible to do new installations of Windows
8? Is it not possible to perform an upgrade of an operating system running in a native VHD?
Cheers,
Trevor Sullivan
If this post was helpful, please click the little "Vote as Helpful" button :)
Trevor Sullivan
Trevor Sullivan's Tech Room
Twitter Profile

Just got word back from someone at Microsoft. They claim that the Windows team confirmed that it was not possible to perform an upgrade of Windows 8 to 8.1 that is configured for native VHD boot or Windows ToGo.
If we take a look at the "limitations" of Native VHD Boot on the TechNet documentation, here is what we find (see below). I don't see anything in there that relates to upgrading the operating system. Seems like a huge gap in the documentation to
me.
How is someone supposed to make a decision to use Native VHD Booting, if they aren't given advance knowledge that upgrading will be unsupported?
http://technet.microsoft.com/en-us/library/hh825689.aspx
Limitations
Native VHD support has the following limitations:
Native VHD disk management support can attach approximately 512 VHD files concurrently.
Native VHD boot does not support hibernation of the system, although sleep mode is supported.
VHD files cannot be nested.
Native VHD boot is not supported over Server Message Block (SMB) shares.
Windows BitLocker Drive Encryption cannot be used to encrypt the host volume that contains VHD files that are used for native VHD boot, and BitLocker cannot be used on volumes that are contained inside a VHD.
The parent partition of a VHD file cannot be part of a volume snapshot.
An attached VHD cannot be configured as a dynamic disk. A dynamic disk provides features that basic disks do not, such as the ability to create volumes that span multiple disks (spanned and striped volumes), and the ability to
create fault-tolerant volumes (mirrored and RAID-5 volumes). All volumes on dynamic disks are known as dynamic volumes.
The parent volume of the VHD cannot be configured as a dynamic disk.
If this post was helpful, please click the little "Vote as Helpful" button :)
Trevor Sullivan
Trevor Sullivan's Tech Room
Twitter Profile

Convert vhdx to vhd

Hi,
Running Server 2012 R2
I have a requirement to convert a vhdx to vhd. I used the builtin feature in the hyperv manager to convert the vhdx (Fixed) disk to a vhd (fixed).
When i create a new server an attach this vhd disk, i get an error when the vm boots. It briefly displays the windows logo, then gives an error: boot failure. Reboot and select proper boot device or insert boot media in selected boot device. This occurs
whether i attach the disk as ide or scsi.
Why would the converted drive no longer be bootable?
Any help would be greatly appreciated
Sean

If the VM was a Generation2 virtual machine, then it is UEFI. And VHD can only be used with Generation1 virtual machines which are BIOS.
The OS in the VM cannot simply handle the bootloader change between BIOS and UEFI.
That is what I suspect is going on.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.

FSMO Rule tranfer - VHD RDC

We have hyper v host with role of Root DC in our setup. we also have DR ADC.
Due to storage issue I had transfer all our FSMO role to our DR ADC. and I tried to compact the root DC VHD. after compact the vhd its not booting I thing its corrupted. we have hyper v backup created before the Role transfer.
can restore the backup and get the RDC. if I restored the VM and power on that. will is cause the FSMO rule.
Kindly help me to come out of this issue.
Best Regards
Jags

You need to proceed as Frank mentioned.
I have started a Wiki to describe Possible Impacts when Putting Online an Old FSMO Role Holder: http://social.technet.microsoft.com/wiki/contents/articles/20420.possible-impacts-when-putting-online-an-old-fsmo-role-holder.aspx
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

2012R2 Checkpoint Backups Fail - "The disk signature of disk1 is equal to the disk signature of disk0"

Before reading any further please note there are no actual disk signature problems per other threads on technet. I mounted all VHD's on the host and none reported offline. I manually checked all VHD disk signatures to the host and all were unique. I loaded
a brand new fresh 2012R2 VM/VHD and at first fine, but after installing updates the problem occurs.
I believe a Windows Update is causing this error but do not know which one. I had a 2012 (non r2) VM that backed up fine, however after upgrading it to 2012R2 integration services and updates, this VM also has the below listed errors. Whether or not there
is only one disk in the VM or multiple the following error is occurring. If I save all the VM's first I get a good and successful backup and checkpoint/snapshot transfers to backup location correctly. It is only when the VM's are running and checkpoint the
process fails.
When a backup is initiated on the 2012R2 host the VM's enter into the backing up state and are still live (not saved).
The following sequence of events occur in the VMs:
Event ID: 58
Source: partmgr
"The disk signature of disk 1 is equal to the disk signature of disk 0"
Event ID: 7036
Source: Service Control Manager
"The portable device enumerator service service entered the running state"
Event ID: 58
Source: partmgr
"The disk signature of disk 1 is equal to the disk signature of disk 0"
Event ID: 98
Source: Ntfs
"Volume E: (\Device\HarddiskVOlume3) is healthy. No action is needed"
Event ID: 98
Source: Ntfs
"Volume F: (\Device\HarddiskVolume4) is healthy. No action is needed"
Event 157
Source: Disk
"Disk 1 has been surprise removed"
I can see in device manager that a Microsoft Virtual Disk is created and then disappears (greys out if viewing hidden devices)
Once Event 157 occurs, the VM's are merged back successfully and the following error occurs on the host.
Log Name: Application
Source: VSS
Date: 4/26/2014 8:00:58 PM
Event ID: 8229
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: SERVER
Description:
A VSS writer has rejected an event with error 0x800423f3, The writer experienced a
transient error. If the backup process is retried,
the error may not reoccur.
. Changes that the writer made to the writer components while handling the event will not
be available to the requester. Check the event log for related events from the application
hosting the VSS writer.
Operation:
PostSnapshot Event
Context:
Execution Context:
Writer
Writer Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Name: Microsoft
Hyper-V VSS Writer
Writer Instance ID: {2aa82577-e446-4340-9afe-1e75fa3a52d4}
Command
Line: C:\Windows\system32\vmms.exe
Process ID: 2088
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="VSS" />
<EventID Qualifiers="0">8229</EventID>
<Level>3</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-04-27T03:00:58.000000000Z" />
<EventRecordID>2254</EventRecordID>
<Channel>Application</Channel>
<Computer>SERVER</Computer>
<Security />
</System>
<EventData>
<Data>0x800423f3, The writer experienced a transient error. If the backup process is
retried,
the error may not reoccur.
</Data>
<Data>
Operation:
PostSnapshot Event
Context:
Execution Context: Writer
Writer
Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Name: Microsoft Hyper-V VSS
Writer
Writer Instance ID: {2aa82577-e446-4340-9afe-1e75fa3a52d4}
Command Line: C:
\Windows\system32\vmms.exe
Process ID: 2088</Data>
I have found no relevant information regarding this error please advice if anyone has opened a case on this and has a reported solution. It appears to be an issue with the new checkpoint process in 2012R2 possibly created by a recent update.
Thanks in Advance

Hi CCPD,
Thanks for contacting Microsoft.
From your description, I learnt that the issue you are experiencing is that you failed to backup VMs when the VM is running. Pleas let me know if I misunderstand anything.
Firstly, please let me know which backup tool you are using to perform backup. And please let mw know how the issue goes if you use Windows Server Backup feature.
After that, please install the Windows Server 2012 R2 newest update rollup as below.
==========================================================
Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: February 2014
http://support.microsoft.com/kb/2919394
Best regards,
Sophia Sun
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

OVM 3.1.1 vhd import

Hi,
I have VHD disks, working well in Virtualbox for Windows. When I import them into OVM 3 (3.0.3 or 3.1.1) they are correctly converted into IMG files but they are not bootable.
That process was working (with th exact same VHDs) in OVM 2.2

Same situation here...but I've solved importing VHDs to VM Virtualbox then exporting the VM created (File->Export Appliance)
In VM Manager import the .ova file generated by VirtualBox as an assembly. Clone the assembly to a template then deploy the VMs by that template.
Hope this helps!!
Greets!!

Encounter Error when trying to inspect VHD

Hi Hyper V Guru,
I am trying to do inspect on the disk of my VM by right clicking the VM-> select settings -> Select Hard Drive -> and click on the Inspect. However I am encountering the error message: "An Error occurred attempting to connect to the
virtual disk management service on computer 'localhost'. Cannot connect to the RPC service on computer 'localhost'. make sure your RPC service is running. what is actually the issue that happen?
Second query: how do I accurately confirm that my VM has no snapshot?
Third Query: if my disk is fixed vhd disk, is it possible to expand it? what are the best procedures and steps of doing this task? what I should notice properly before expanding? will there be any risk of expanding VHD? as this is our production
exchange server and very critical, I am really worry of doing this.
Thanks for your attention.
Regards,
Henry

Hi Henry,
I assume that you are using server 2012/r2 .
Are you using RSAT to do Inspect disk ?
If yes , here is a similar thread :
http://social.technet.microsoft.com/Forums/windowsserver/en-US/4b8fb53b-0fd4-4300-b566-0de9b570e243/upgraded-to-hyperv-server-2012-r2-now-getting-rpc-server-unavailable-error?forum=winserverhyperv
“ Second query: how do I accurately confirm that my VM has no snapshot? ”
Using the cmdlet :
get-vmsnapshot -vmname <the name of your vm >
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Boot from VHD generates Error 0xc03a0001

So I created a VHDX which contains an installed windows 7 environment.
Booted my windows 8.1 environment, attached the vhdx and added the VHDX environment to my boot.
BCDBOOT F:\WINDOWS
Reboot, choose windows 7 and get this error;
0xc03a0001 -> An unexpected error has occurred.
When I lookup this error, it means "The virtual hard disk is corrupted. The virtual hard disk drive
footer is missing."
So I re-created the vhdx and the system on it, but it spawns the same error.

i found this article maybe very useful to investigate your issue
http://reboot.pro/topic/16141-troubleshooting-os-boot-from-vhd/
VHD BOOT TROUBLESHOOTING
VHD boot problems are rare, when following exactly the Tutorials linked in this Post Signature. Most are caused by a corrupted BCD (Boot Configuration Datastore) or missing boot-critical disk & controller drivers, enabling reading the VHD or hard disk
where its saved. If they occur, follow the troubleshooting steps for natively supported & unsupported OS boot from VHD:
1) install latest Windows Virtual PC (with 1024Mb+ RAM assigned), attach Win7 VHD to it as IDE disk and try to boot as hard drive. If it doesn't, it may be because of missing or errors in BCD, missing Bootmgr, mismatch of disk Sig, or incorrect partition
offset set in BCD, DetectHAL element is Off or missing, missing disk driver, or volume wasn't marked Active. This may occur, since Win7 & ThinPC may lack BCD sample store in their WindowsBoot folder, resulting in wrong BCD structure when using BCDBoot
command to add BCD to the new VHD. To fix, use suggested repair sequence. However, if you face 0x7B error during boot from VHD, you may need to add missing disk driver(s) entries to VHD's OS Registry, and add the driver installation packages, so that OS can
autoinstall the drivers after boot. Read this and that explanation threads, and use suitable tools, like included with IMG_XP driver utilities and its collection of Registry fixes. Or, once you found missing driver INF packages, attach the VHD, mount its OS
Volume to an empty folder and inject the drivers offline with DISM as per Install Unsupported OS to VHD Tutorial. If the VHD boots after that, proceed to step 2.
2) copy that Win7 VHD from HD to a bigger fixed contiguous VHD, add boot environment to the bigger VHD disk with EasyBCD or Visual BCD Editor installed on your system HD, add Win7 boot entry to it, attach the big VHD to Win VPC as IDE disk, try to boot Win7
from VHD natively inside VPC. If it doesn't, fix the big VHD's BCD using the below repair sequence. After it does, proceed to step 3, if you want test booting with Grub4DOS & WinVBlock.
3) add Grub4DOS to the big VHD, fully install WinVBlock to Win7 after booting it natively from VHD or as IDE disk inside VPC, make Win7 VHD contiguous, attach the big VHD to the Win VPC as IDE disk, try to boot Win7 VHD from it via G4D & WinVBlock menu.
If errors, try to find matching versions of Grub4DOS & WinVBlock (older G4D may work well with WinVBlock - Feb. 2011, can take from wimb's IMG_XP folder). If Grub4DOS shows "File not found" error on boot, and the file name is correct in its Menu,
the problem seems to be in mounting the large VHD disk. You must reboot G4D to continue tests or restore original disk mapping. Make sure to test sign WinVBlock 64-bit, and switch On Test Mode in Win7 64-bit, or use F8 at boot. Should boot... but at times
WinVBlock disk may cause OS instability & file access issues after boot.
Boot troubleshooting requires some practice, so easy way to start - native boot VHDs & EasyBCD.
REPAIR BCD STORE WITH VISUAL BCD EDITOR
- Boot Win7 from your host drive, attach the VHD with related to BCD boot problems, when attached to VPC as hard drive
- Make sure OS volume on VHD is marked as Primary & Active, and mount it as V: drive
- Start Visual BCD Editor, open BCD Store from V:BootBCD
1. If there is no BCD Store on the VHD:
- Select Repair Boot Record from Menu, select V: , tick Vista/7&Fix MBR --> OK,
- Select Repair BCD from Menu, BCD Drive V: , Win7 folder V:Windows --> OK
- Exit Visual BCD Editor, detach the VHD and reboot in VPC to check if the errors were fixed
2. If there is BCD Store on the VHD:
- Delete all entries under Loaders section on the Left Pan
- Click Edit Boot-Menu, delete all Boot Entries from the DisplayOrder list
- Proceed to Repair Boot Records, then Repair BCD from Menu
- Reload BCD from the VHD by selecting Open Store again from Menu
- Add any missing OS Loaders in Loaders section on the Left Pan, and rename their entries as you like
- Click on each entry on the Left Pan, and inspect its elements on the Right Pan. Make sure they make sense for the hard drive boot, are similar to a reference VHD's BCD that boots OK (GUIDs may differ), and linked to correct BCD Objects GUIDs
- Click Edit Boot-Menu, and add or edit boot entries list and display order to match Loaders list on the Left Pan
- Exit Visual BCD Editor, detach the VHD and reboot in VPC to check if the errors were fixed
REPAIR BCD STORE WITH EASYBCD
You can use EasyBCD instead of Visual BCD Editor to create or repair a BCD store:
- Install and start EasyBCD
- Select BCD Store on the VHD, using File Menu and open it
1. If there is no BCD Store:
- select BCD Deployment on the Left Pan, click Install MBR, then select partition V: --> Install BCD
- Click Add New Entry --> Windows Vista/7 --> Drive V: --> Add Entry
- Exit EasyBCD, detach the VHD and reboot in VPC to check if the errors were fixed
2. If there is BCD Store:
- select BCD Backup/Repair on the Left Pan, tick Recreate/Repair Boot Files --> Peform Action, then tick Reset BCD Configuration --> Perform Action
- Exit EasyBCD, detach the VHD and reboot in VPC to check if the errors were fixed
- If not, reattach the VHD as V: drive, open Console, run bcdboot v:windows /s v: to recreate BCD manually
- Detach the VHD and reboot in VPC to check if the errors were fixed
- If not, boot from the VHD natively from the host's Boot Menu (if its OS supports native boot from VHD), install EasyBCD and try fixing VHD BCD Store and boot sectors with it, then test boot again
- If it still doesn't boot, and you added all required boot time drivers to OS on the VHD, post the exact boot error and Windows Safe Mode driver load step, when the error occurred, in a new thread asking for help.
sorry for the long copy paste

Installing Hyper-V Powershell Module on Virtual Machine

I have a situation where I am running Hyper-V 2012 and have several virtual RemoteApp RDS servers (server 2012 R2) with a user profile disk server (also 2012R2 virtual machine) that stores all of the VHDX user profile disks. I want to perform some maintenance
on the VHDX files by running optimize-vhd to compact the disks to keep them from being larger than they need to be. Anyhow, that PowerShell commandlet won't run unless the Hyper-V module is installed but in order to install it, the Hyper-V role must be installed.
Since it's a virtual machine, it's not supported to install the Hyper-V role (although I hear it may be possible) so I was wondering if it is possible to install only the Hyper-V PowerShell modules. I would just use a Hyper-V server to run it but the commandlet
does not seem to allow UNC/Share paths. Any suggestions? Thank you in advance for your time!

Hi Scott,
I tested on my hyper-v enviroment, and installed the feature "Hyper-v Module for Windows Powershell" on VM, and I could run the cmdlet "optimize-vhd", however, It couldn't run successfully without Hyper-v Role installed:
In addition, if you just want to compact the vhd file on vm, how about using the command "DiskPart":
You can then complete the compacting using diskpart from a Command Prompt:
Run diskpart
Select the disk via its path: select vdisk file="<path>"
Attach it as read-only: attach vdisk readonly
Compact it: compact vdisk
Upon completion of the compact, detach it again: detach vdisk
You can then re-attach it via Disk Management in its normal and newly compacted state
Refer to:
https://fiddley.wordpress.com/2014/01/27/dynamically-expanding-vhd-not-compacting-in-hyper-v/
If there is anything else regarding this issue, please feel free to post back.
Best Regards,
Anna Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Determining a Device That Does Not Exist

Hello,
We have a Citrix Xendesktop 7.1 PVS environment. The VHD disks are hosted on a volume on a Windows Server named S00CITRIXVHD01 that has 2 disks C drive(Disk0) and D drive(Disk1). In the event log of the server hosting the VHD disks I see this almost
every day:
The device, \Device\Harddisk3\DR145, is not ready for access yet.
Harddisk2 is also in some log entries. The only problem is the server does not have a harddisk2 or hardisk3 in the Disk Management GUI. However If I open the registry to HKLM\Hardware\DeviceMAP\SCSIPORT2\SCSIBUS0 there are reg keys for:
Target Id 0
Target Id 1
Target Id 2
Target Id 3
Target Id's 0 and 1 have info in them as I would expect but 2 and 3 are empty. I see other event log entries
Event ID 50:
{Delayed Write Failed} Windows was unable to save all the data for the file . The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.
Event ID 157:
System
Provider
[ Name]
disk
EventID
157
[ Qualifiers]
32772
Level
3
Task
0
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2015-03-10T01:27:30.545675300Z
EventRecordID
275973
Channel
System
Computer
S00CITRIXVHD01.f.q.d.n
Security
EventData
\Device\Harddisk3\DR145
3
0000000002003000000000009D000480000000000000000000000000000000000000000000000000
Binary data:
In Words
0000: 00000000 00300002 00000000 8004009D
0010: 00000000 00000000 00000000 00000000
0020: 00000000 00000000
In Bytes
0000: 00 00 00 00 02 00 30 00 ......0.
0008: 00 00 00 00 9D 00 04 80 ......€
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
So now I have these mystery disks that aren't ready, then have an error and then surprise disconnect and I can't figure out what they are or why they are logging errors. I would appreciate any insight anyone can offer on how
to track down what these drives are.

Hi Rich Ellis-MC,
If you are using Serve 2012r2 please try to install the following update then monitor the issue again.
Extraneous log entries are created when you remove virtual disk devices in Windows 8.1 or Windows Server 2012 R2
http://support.microsoft.com/en-us/kb/2958027
Most of the similar issue occur when there have backup soft ware running or there have hardware issue, please try to stop the backup software then monitor this issue again,
in your environment try to ask citrix may get more tips.
More information,
Description of the Event ID 50 Error Message
http://support.microsoft.com/en-us/kb/816004
Disk 0 has been surprise removed EventId: 157
https://social.technet.microsoft.com/Forums/en-US/9feed539-493a-4fbe-9c75-d5619bedc2a9/disk-0-has-been-surprise-removed-eventid-157?forum=windowsserverpreview
Error in virtual machine event log "disk 1 has been surprise removed"
https://social.technet.microsoft.com/Forums/en-US/70d8cbee-a189-4555-80c1-3b19ebb51d0c/error-in-virtual-machine-event-log-disk-1-has-been-surprise-removed?forum=winserverhyperv
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

5800 xm - bug or what else... it restarts itself a...

Hi all,
I'm the (for everything else lucky) owner of a 5800 XM, that works almost great.
Dunno what's the cause, it resets itself (does a partial reboot, showing the white screen with the Nokia blue logo) in several ordinary use circumstances. For example, it will almost certainly reset itself after sending an ordinary text message.
Already tried hard resetting, firmware upgrade, etc... never formatted my memory card, btw, and always restored settings from backup.
I even tried reinstalling firmware (31.0.101) but didn't solve.
Ideas?
Thanks!!!

The file extension .wlz refers to a WinImage file
WinImage:
"WinImage is a fully-fledged disk-imaging suite for easy creation, reading and editing of many image formats and fileystems, including DMF, VHD, FAT, ISO, NTFS and Linux. The disk image is an exact copy of a physical disk (floppy, CD-ROM, hard disk, USB, VHD disk, etc.) or a partition that preserves the original structure. With WinImage in place, you can recreate the disk image on the hard drive or other media, view its content, extract image-based files, add new files and directories, change the format, and defragment the image. All this and more is delivered in one intuitive user interface that enables imaging right out of the box"
in http://www.winimage.com/winimage.htm
I don't really understand how did those files ended up in ur phone but probably it was due to a wrong file copy...
Eric

VHD disk compact

Similar Messages

Maybe you are looking for