Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

1 Neutral

About RUSerious

Contact Methods

  • Website URL

Profile Information

  • OS
    Windows 10 x64
  • Country

Recent Profile Visitors

1,018 profile views
  • xper

  1. Anyone figure out how to do a feature / build / version update (1703 to 1709) within a VHDX file? Normal updates (Win+X > Update & security) work fine, but MS will not allow version updates on a USB or VHD / VHDX drive. Tried obvious of mounting / attaching the VHDX, then cloning it to an internal partition, and then editing BCD to boot to the clone. Acts likes it going to boot to the VHDX clone (on the internal HDD partition), but just ends up with the eternal gray screen. Familiar with BOOTICE if that helps...TIA
  2. The first couple posts of this thread are a bit confusing as to what is the best tool or combination of tools. Would be nice to edit those to clarify what is now known to be the best method... Thanks
  3. That was my first thought, since the retail shelf does get pretty outdated. But still, never would have expected the USB 3.0 drivers on top of the line laptops to be that bad -- right out of the box. Thanks
  4. Wanted to see what the actual top speed of an mSATA SSD in an mSATA USB 3.0 enclosure might be, so went to a retail store with several top of the line laptops. Tried 5 of the highest priced laptops they had and was surprised that only one was over 400 MB /s. Even more surprised that 3 where barely over 100 MB / s. And yes, the SSD was plugged into ports that were clearly marked with the 'SS' for USB 3.0. Was using Crystal Disk Mark on one partition of the SSD to run tests on another partition of the SSD. Any ideas for why these top dollar laptops had such poor USB 3.0 performance? Guess it pays to test before you buy.
  5. Good to know, Thanks jaclaz BTW, found an easy way to get an XP VHD. Use these instructions to get the VHD from MS: http://www.picohelp.com/1264/how-to-run-windows-xp-in-windows-8-with-virtualbox-6-simple-steps.html If your not on Windows 7, and can’t extract from the WindowsXPMode_en-us.exe file, then run that exe file and make a copy of the extraction folder (it creates) before clicking OK on the Windows 7 ONLY message (which deletes the extraction folder). Then use the tips in link above to get to the actual XP VHD. Then use a VM app as in link above to run the VHD.
  6. YES, THANK YOU. Did this: Bootice >> BCD Edit >> Set Default (made no difference). Then did this: Bootice (Physical Disk tab, system / boot partition chosen) >> Process PBR >> BOOTMGR (NTLDR was already selected, changed to BOOTMGR) >> Install / Config And that did it .!! Did not change / Process MBR since Windows NT 5.x / 6.x MBR was already selected. Bootice (Physical Disk tab, system / boot partition chosen) >> Process MBR >> Windows NT 5.x / 6.x MBR
  7. Desperate for help. Tried to install Windows XP to use a good laser printer (no good drivers after XP). Tried to use WinNTSetup v3.8.6 to make a XP VHD – no go. So then tried to use WinNTSetup v3.8.6 to install Windows XP to a 4 GB partition. Used my system / boot partition (with BCD files) as the boot drive. All seemed to go well until reboot and XP install said it could not find all the install files needed. Now stuck with a system that will only boot to a blue install error screen. Have EasyBCD and BOOTICE and tried to remove any reference to WindowsXP in any BCD files I could find on any partition – but system still wants to boot to the Windows XP install error screen. Now booting to system from a portable drive – that if I remove, system freezes. Don’t want to mess it up any worse. So could someone PLEASE tell me how to remove whatever it is that will not allow my normal BCD options to load at boot. MANY Thanks
  8. Yes, I used WinNTSetup to install 8.1 to a VHD (don't remember all the details (relearn when I do 10)). I keep a VHDa to use / update, and a VHDb to boot to for when I want to back up VHDa (both on my HDD). One issue is that VHDa keeps growing in size -- by GBs. I don't know the cause of these huge increases as recovery images have been disabled. And hard to imagine that normal MS updates are adding this data. Will hopefully figure this out when I do 10.
  9. Fantastic! Works like a charm. Thanks
  10. For easy testing of the VHDXs that diskmgmt creates, can drag a shortcut of W:\Windows\System32\diskmgmt.msc to desktop. See the diskmgmt "Action" menu. Hope that helps. diskmgmt might attach the VHDX when it is created and that error might be from trying to attach a VHDX that is already attached. Don't see a way to detach the VHDX via diskmgmt. Sorry if that confused things.
  11. Are you saying that WinNTSetup actually does create a VHDX, and that we can just edit extension to =.VHDX manually? Or does the parameter error indicate some other issue? VHDX does offer some nice features. Thanks for your work.
  12. Thanks for the update. Great app. Is VHDX support still missing? Booted to a WTG VHD, win8.1 enterprise, as host. Can create VHDX via MS Disk Manager (on a separate partition I use for all my VHDs), but when try to WinNTSetup attach this VHDX, WinNTSetup gives error -- parameter is incorrect. Still not able to get WinNTSetup to create a VHDX file -- extension always VHD.
  13. On this page for Windows To Go: Feature Overview http://technet.microsoft.com/en-us/library/hh831833.aspx Under differences it states: “Internal disks are offline. To ensure data isn’t accidentally disclosed, internal hard disks on the host computer are offline by default when booted into a Windows To Go workspace. Similarly if a Windows To Go drive is inserted into a running system, the Windows To Go drive will not be listed in Windows Explorer.” Which made me think maybe it should be set as “ * “ for “Mount Installation drive as” for WTG to work as stated. Thanks
  14. The reason for setting it at W: was to prevent partition letter shuffling. But at W: did NOT prevent partition letter shuffling. So thought I would try * for WTG and see if that would allow WTG to NOT shuffle partition letters. edit: Would WTG still boot as C: even if I set “Mount Installation drive as” to '*' ??
  15. Well, I tried to do this with Regedit, but mucked something up -- eternal preparing windows dots... So, for my start-over, Should it be ok to set “Mount Installation drive as” to '*' for a Windows To Go drive? Or would this also give the eternal dots circle? Thanks
  • Create New...