Hi, I recently installed a bad driver onto Windows 7 Ultimate (the Realtechttp://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=24&PFid=24&Level=4&Conn=3&DownTypeID=3&GetDown=false#HighDefinition Audio Codecs) and the recovery utility in the boot menu fails to recognise it even after I go into the command prompt option and type in the following commands. Diskpart select vdisk file=D:\Win7x86.vhd attach vdisk The process completes sucessfully and then I type in "list vol" and it lists the drive as G:\. I rerun the startup repair tool and it keeps failing. What would I have to do to get the recovery utility to work? Do I have to create a startup script for diskpart in WinRE? If so, how would I create a script to do just that? And further more how would I integrate it into the WinRE image? I'm doing the VHD image boot. /script/ C:\Windows\system32>bcdedit /v Windows Boot Manager -------------------- identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795} device partition=\Device\HarddiskVolume2 path \bootmgr description Windows Boot Manager locale en-US inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e} default {933c82b2-ee27-11df-955d-d0d5d5a8607d} resumeobject {eec19175-f06e-11df-9ff1-806e6f6e6963} displayorder {933c82b8-ee27-11df-955d-d0d5d5a8607d} {933c82b2-ee27-11df-955d-d0d5d5a8607d} {933c82b4-ee27-11df-955d-d0d5d5a8607d} toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d} timeout 10 displaybootmenu Yes Windows Boot Loader ------------------- identifier {933c82b8-ee27-11df-955d-d0d5d5a8607d} device vhd=[C:]\Server08R2.vhd,locate=custom:12000002 path \Windows\system32\winload.exe description Windows Server 2008 R2 locale en-US inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7} recoverysequence {933c82b9-ee27-11df-955d-d0d5d5a8607d} recoveryenabled Yes osdevice vhd=[C:]\Server08R2.vhd,locate=custom:22000002 systemroot \Windows resumeobject {933c82b7-ee27-11df-955d-d0d5d5a8607d} nx OptIn Windows Boot Loader ------------------- identifier {933c82b2-ee27-11df-955d-d0d5d5a8607d} device partition=C: path \Windows\system32\winload.exe description Windows 7 Home Premium (x64) locale en-US loadoptions DDISABLE_INTEGRITY_CHECKS recoverysequence {933c82ac-ee27-11df-955d-d0d5d5a8607d} recoveryenabled Yes osdevice partition=C: systemroot \Windows resumeobject {eec19175-f06e-11df-9ff1-806e6f6e6963} sos No debug No Windows Boot Loader ------------------- identifier {933c82b4-ee27-11df-955d-d0d5d5a8607d} device vhd=[C:]\Win7x86.vhd ,locate=custom:12000002 path \Windows\system32\winload.exe description Windows 7 Ultimate (x86) locale en-US inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7} recoverysequence {933c82b5-ee27-11df-955d-d0d5d5a8607d} recoveryenabled Yes osdevice vhd=[C:]\Win7x86.vhd ,locate=custom:22000002 systemroot \Windows resumeobject {933c82b3-ee27-11df-955d-d0d5d5a8607d} nx OptIn /script/ Copied from my other post which has stalled. - http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/80fa078e-c972-47cf-aa81-ad2141592d41

Hyper-V virtual machines do not start after using Startup Repair http://blogs.msdn.com/b/virtual_pc_guy/archive/2010/01/19/hyper-v-virtual-machines-do-not-start-after-using-startup-repair.aspx You may note that Startup Repair does not repair the virtual system. Therefore you cannot use it to repair your Windows 7 Ultimate system. Doing a system restore in the virtual system is a way to resolve the issue. Another way is roll back the audio driver.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.

This is not a Hyper-V System. This is a VHD booted OS straight of the 1st partition then Win7x86.vhd http://blogs.technet.com/b/aviraj/archive/2009/01/17/windows-7-boot-from-vhd-first-impression-part-1.aspx

I know that. I just wanted to tell you that you cannot do Startup Repair to repair the virtual system.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.