Hasleo Software Forums

Full Version: USB functionality during WinPE cloning
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3
Ok, first of all, I have to say thank you everybody who tries to help me, but so far no success.
I started again from the beginning and added the specific driver for my laptop. This is iusb3xhc.inf.
But it's not working, always specified disk not found.
I checked the BootWIM directory, the driver is not in the windows\inf directory.
By the way, at the beginning WintoUSB made WinPE, then not more.
I always have to de and reinstall WintoUSB to get the WinPe functionality.
It's not clear what the SW exactly is doing.
I'm using version 2.4 because this version is doing the Cloning.
I would really buy newest version 3.2 if I would know, that it is working.....in my case.
Please download Windows 10 PE from the links bellow and try again. Please download 64-bits WinPE if your windows operating system is 64-bits, otherwise downlad 32-bits WinPE.
You need to put boot.wim and boot.sdi in bin folder under the installation directory fo WinToUSB, then try cloning.

64-bits Winpe:
http://www.easyuefi.com/wintousb/downloa...4/boot.wim
http://www.easyuefi.com/wintousb/downloa...4/boot.sdi

32-bits Winpe:
http://www.easyuefi.com/wintousb/downloa...6/boot.wim
http://www.easyuefi.com/wintousb/downloa...6/boot.sdi

Reference:
How to determine whether a computer is running a 32-bits version or 64-bits version of the Windows operating system:
https://support.microsoft.com/en-us/kb/827218
Sorry but I don't understand
I want to clone my Windows 7, what shall I do with WinPE Windows 10?
Ok, nevertheless, I did what yo've been recommended, but still the same "specified disk not found" !!!
As I mentioned on a different posting.
WintoUSB does not create the BootWIM directory.
It is doing it just one time after the installation procedure, that's it.
Any explanation?
Another thing
When I want o get more information of installed drivers in the image, I tried the dism option /Get-drivers ,
but it doesn't work. dism wants me to provide the image .
So when I try to mount the image ( provide ) once more, than dism comes up with " image already provided"
'm really getting crazy more and more. !!!!!!!
So the best would be not wasting so much time any more and give it up.
WinToUSB will boot into the Windows PE to complete the system clone. And Windows 10 PE contains USB 3.0 driver by default, if Windows 10 still can't recognize the USB device, then I can't help you more.
Thanks , after all, the cloning process started and completed now successful.
But when I tried to boot from this stick, it doesn't.
On the USB Stick there's just one (115GB) file called WintoUSB.VHD, no other files ( system and all files are not hidden )
Could it be, that the Stick is not formatted correctly as a Boot Stick ??
But this is normally done from WintoUSB during the cloning startup, isn't it?
I checked the Stick ( Very fast, reading aprox. 150MB/s) in Windows. There's a primary 115GB partition and a 100MB partition, that's all I see.
And why VHD ?? Shouldn't it be legacy? But at the startup process I can't chose legacy !! It's grayed out.
Hope I'm not nerving, but WintoUSB is a complicated SW and doesn't do everything.
So in my eyes you have to be really a Windows specialist.
Hope of a finally help

And in advance, I appreciate your help and to honor it, I bought WintoUSB right now.
But just wondered aboz your price. 29,99$ should be aprox. 27€, I payed 37...€ ( 10€ tax thats miore than 30% ?? )
With the newest version I tried to format the USB Stick and got the following ( never had before ) error message:
" Start of the System API failed", which I didn't get with the version 2.4
Now I payed 37€ and can't even format the stick...............disappointing !!
(10-29-2016, 09:07 PM)Zppianer Wrote: [ -> ]With the newest version I tried to format the USB Stick and got the following ( never had before )  error message:
" Start of the System API failed", which I didn't get with the version 2.4
Now I payed 37€ and can't even format the stick...............disappointing !!

Please accept our apologies for any inconvenience we have caused and thank you for reporting this problem. Please send the user.log file to us (via e-mail at: [email protected]), it is located in the bin folder under the installation directory, and we will resolve it as soon as possible. Thanks.
Ok, log file has bee sent.
Pages: 1 2 3