Hasleo Wintousb users Broken again


  1. Posts : 11,246
    Windows / Linux : Arch Linux
       #1

    Hasleo Wintousb users Broken again


    Hi folks
    Anybody using Hasleo Wintousb for creating Windows systems on bootable external USB devices (aka Ms Windows to go) -- the latest insider build of Windows (version 1809 build 18305.1003) breaks it again I'm afraid

    Pity as this is a good way of testing these builds on laptops without having to mess around with unnecessary backups etc. SSD connected via sata-->usb3 on a laptop gave astonishingly good performance so a valid way of testing on real hardware too without having to use a VM.

    I'll see what HASLEO come back with - I've sent details to their support dept --they were quite quick last time there was an issue with this product.

    Cheers
    jimbo
      My Computer


  2. Posts : 43,279
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #2
      My Computers


  3. Posts : 11,246
    Windows / Linux : Arch Linux
    Thread Starter
       #3

    Hi folks
    Got a reply from Hasleo saying essentially that as there were too many builds in the insider rings that change too much they don't have the staff to keep up with this so they will concentrate on the officially released versions of Windows .

    The current version of windows (1809 build 17763.195) runs the software just fine.

    I'll mark as solved as only current standard released versions of windows will be supported.

    Cheers
    jimbo
      My Computer


  4. TbO
    Posts : 11
    Windows 10 x64
       #4

    Indeed the problem with all insider builds after 1809 still shows that MS didn't address this issue. There is however a workaround to make a WinToGo USB disk for all. I already posted this on the answers.microsoft.com site.

    Just prepare your USB as usually with WinToUSB or any other way then go into the drivers section on the USB disk and do the following:

    a) rename the uaspstor.sys to uaspstor.sys.old or whatever you like

    b) copy usbstor.sys uaspstor.sys

    Practically you now have 2 usbstor.sys, but one is named uaspstor.sys.

    You might need NSudo to do it.
      My Computer


  5. Posts : 11,246
    Windows / Linux : Arch Linux
    Thread Starter
       #5

    Hi there @TbO

    Viele Danke !!!

    Quickest method yet -- worked a treat

    I test these new builds out on a spare laptop - it's really easy, convenient and fast using external USB3 (SSD via USB3->SATA connector) so I don't have to mess with anything on the internal HDD on the laptop. SSD is easily fast enough for running windows this way and I've several spare SSD's which allow me easily to test different builds without hassle of backup and restore to laptop's internal SSD.

    I just plug the external SSD in and boot -- Easy !!

    For renaming the two files I just plugged the SSD into a Linux system to get round "Need admin privilege" or not authorized when renaming the windows system files.

    I recommend this method of testing to anybody who wants quick way of testing these builds and doesn't have a spare computer. You'll need SSD and a USB3-->SATA connector.

    Cheers
    jimbo
      My Computer


  6. TbO
    Posts : 11
    Windows 10 x64
       #6

    Hi @jimbo45, did you see with latest insider builds that MS fixed the problem? Now it works out of the box with external USB disks. Well at least, even if they never acknowledged the problem.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 18:49.
Find Us




Windows 10 Forums