02-10-2026, 03:15 PM
(09-23-2025, 11:46 AM)admin Wrote:Ok, many thanks for confirming this.(09-23-2025, 04:08 AM)SwimmeRM Wrote: Hello all,
after WinToUSB Free v10.0 setup completed I also was happy to notice that it already included own x64 version of its executable.
But why after WinToUSB 10.0 setup completion, its x64 executable icon was not created and so enabled for its direct execution on my x64 OS (Windows 7 SP1 x64 Ultimate) ?
I mean the 'Hasleo WinToUSB' icon it created only into its own menu (with same name) into Programs (since I choose not to create another one also on Desktop) would have been better if created to launch its x64 executable icon ('C:\Program Files\Hasleo\WinToUSB\x64\WinToUSB\bin\WinToUSB.exe') rather than only having x86 version icon created ('C:\Program Files\Hasleo\WinToUSB\bin\WinToUSB.exe').
Or otherwise setup might have been a little smarter to possibly let me choose if I preferred to run x64 version icon only or even propose me to have both x64 and x86 version icons rather than simply forcing me to only be able to choose x86 version icon.
What do you think about this ?
Thanks in advance for anyone else attention and quite obviously more related comment on this.
Best Regards
Rob
The files installed in the x64/x86 folders are used to create WinPE, which allows you to boot into WinPE and perform cloning operations when a system snapshot cannot be created properly. You should always load the program via C:\Program Files\Hasleo\WinToUSB\bin\WinToUSB.exe.
It also seems that before asking I didn't properly checked that WinToUSB.exe inside 'C:\Program Files\Hasleo\WinToUSB\bin\' and 'C:\Program Files\Hasleo\WinToUSB\x64\WinToUSB\bin\' indeed had already same size, so to also mean that version inside 'C:\Program Files\Hasleo\WinToUSB\bin\' was already an x64 version and not an x86 like I thought initially... :-o :-s 0:-)
BTW ITMT I also just upgraded what in mid January already became v10.4 to current/latest v10.5 .
Best Regards
Rob
