Jump to content











Photo

Inaccessible Boot Device Windows To Go VHD on a UFD


  • Please log in to reply
4 replies to this topic

#1 Noer5

Noer5

    Member

  • Members
  • 34 posts
  •  
    Tahiti

Posted 11 March 2015 - 03:17 PM

Booted to Windows To Go VHD (W).
Used Aomie Backupper to clone W onto UFD (F).
Added bootmgr and /Boot to root of F.
Used only a single partition on UFD (F) for all files.
Used Bootice to make F Active and Install / Conf MBR.
Boot to UFD, get Blue Windows Icon, then get error ‘Inaccessible Boot Device’.

Is this just Windows seeing that it is on a UFD and not allowing that?
Or am I doing something else wrong.

I've tried keeping Windows To Go within a VHD, but keep getting same error?
Thanks
 



#2 steve6375

steve6375

    Platinum Member

  • Developer
  • 7566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films
  •  
    United Kingdom

Posted 14 March 2015 - 08:45 PM

Does this help?

http://www.rmprepusb.com/tutorials/129

Otherwise give details. Win 8 or 8.1, 32-bit or 64-bit, UEFI or MBR boot, Fixed USB disk or Removable USb disk, How is BCD set up, etc.



#3 Noer5

Noer5

    Member

  • Members
  • 34 posts
  •  
    Tahiti

Posted 15 March 2015 - 08:02 AM

Thanks Steve,

In that tutorial, in step 4, are we supposed to let it finish setup and reboot to complete installation?

Or are we supposed to stop it at some point, Tweak the BCD as in step 5, and then finish the install?

What does it mean to install to both boot drive and VHD?



#4 Noer5

Noer5

    Member

  • Members
  • 34 posts
  •  
    Tahiti

Posted 15 March 2015 - 02:50 PM

More specific:

WinNTSetup provides info pop-up “This stage of Setup is done, after Reboot the SysPrep Phase will begin.”

Are we supposed to Tweak the BCD before going on to the SysPrep Phase?

 

"4. Install Windows to the Boot drive and VHD"

What does it mean to install to both boot drive and VHD?

 

Also:

If VHD is dynamically expanding with a maximum size of 19 GB (set by WinNTSetup),

and if nothing else is placed on the VHD's PTN,

should a 21 GB PTN be large enough for this 19 GB VHD?

 

Thanks



#5 Noer5

Noer5

    Member

  • Members
  • 34 posts
  •  
    Tahiti

Posted 18 March 2015 - 01:59 PM

Pretty sure I found the cause of the problem.

Had the microdrive filter driver installed on the Host system that I was working with the VHDs on and that may have somehow made them not accessible. Any more insight on this?

Hopefully help save others a lot of headaches.

 

This page has some good info on VHDs

https://technet.micr...MK_requirements

with the need to leave space for the page file being the largest space concern.


Edited by Noer5, 18 March 2015 - 02:05 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users