I'm very surprised to hear that. The WIM image that's executed after BOOTing the UFD is exactly the same WIM image that's used when running Hasleo from the BOOT menu. That image is where all necessary drivers reside. I need to think about this a bit... sounds like you're using two different WIM image sources (old UFD maybe... old BOOT menu maybe).
You can try the following if your BOOT menu works OK... The WIM used by the BOOT menu is located in the "boot" folder located in the C: drive root. It will have a cryptic name.WIM. Mount your Emergency Disk UFD, go to the "sources" folder and rename the "boot.wim" file to "boot.old" (preserviing it locally). Then copy the "CrypticName.WIM" to the "sources" folder on your UFD and rename the file to "boot.wim" Try BOOTing from the UFD once again and see if it's supporting your TrackPad. If it isn't, that your current WIM used for the BOOT menu is not one actually being used by the BOOT menu (some users like me don't let Hasleo build its BOOT menu... I install the WIM from my built ISO Emergency Disk into the BOOT menu instead, maybe you do the same).
Oh, i misinformed. I am without mouse in both occasions. So it probably is a pc flaw, or? On my other pc i can add 3 drivers to get it to function, on this one there where only 1 to add. I suppose it will be the same using Easy BCD.
EasyBCD has nothing to do with it, it's the building of the WIM image where the driver(s) are needed, whoever the WIM may be used (UFD, BOOT menu, wherever).
So it is the end of the road then?! No other driver to add which can fix it? I used my IFW license and created a UFD, no problem with the mouse. Full support in restore environment.
I have exactly the same issue on an SSD system where the mousepad doesn't work with the Hasleo boot menu or USB. I haven't tried another imaging software on the system. There is no mouse driver for the system on the manufacturer's website. The Windows device manager shows "HID-compliant mouse" under Mice and other pointing devices.
@pb1 - What LIVE OS on your Systems are you using for these tests (reaching for straws here) and can you tell whether IFW is using the resident System's WinRE to build its media?
W11 Home 24H2 - .3476. I built a Windows restore media UFD, the top alternative. Not uefi, linux etc.
I'm not really sure what your statement above means. Your BiOS will support UEFI BOOTing and possibly Legacy-MBR BOOTing as well.... nothing to do with Linux/Windows other than where the BOOT process takes you. When you say you built the "Windows Restore media UFD, the top alternative," what does that mean? Is that a Windows Restore disk, and if so, how did you integrate Hasleo directly into that disk (it's not an option in HBS). I'm just trying to find out exactly what you're using for your UFD BOOTing. Was your IFW Recovery Media produced by IFW directly... same question for your Hasleo Recovery Media?
The bios only support uefi, nothing else. The UFD mentioned above that i did was with IFW from within, same with HBS, and when doing it you get several alternatives in a row, the top one is Windows recovery media and the bottom one is uefi media. So not the PE alternative.
Thank you for the effort and suggestion, but unfortunately, still no mouse They have a different way of doing things with this, only .inf files work.
Yes i know. But i am thinking future. Hopefully HBS will survive IFWs functionality. Besides, i like the simplicity of HBS.
I don't have that laptop anymore. If I remember well, it had an Elan driver and no WinPE issue. I use the PS/2 Compatible Mouse option under Mice and other pointing devices on an HDD laptop, as the supported Synaptic driver intermittently hangs the mouse. I have no Hasleo WinPE issue on that HDD laptop. The PS/2 Compatible Mouse option is not available on the mentioned Lenovo laptop.
For those with interest... an anomaly was discovered when adding INCs to an existing broken chain (missing image), no errors were discovered. This anomaly wasn't discovered until attempts were made to restore using the broken chain... not a good time to find out it was broken. A discovery was also made that when trying to restore a time point prior to the chain break, it would fail as well... no need for that to happen. Anyway, anomalies were reported over the last few days and a test fix was delivered this morning (available HERE, if needed). This team has been very responsive... There is also an anomaly with the version referenced above... pls read HERE for details.
@ TheRollbackFrog I have an issue I installed the version above, made new boot menu and usb recovery When I entered the pre boot menu to do a restore BSOD, I thought no big issue I will use my usb disk booted into recovery disk and BSOD, I was left unable to recover the system, this was with the test fix..
@warrior99 - I need to know more about that BSOD... what did it say? Sounds like the build (same WIM for both the BOOT menu and the UFD) has some issue (try again...??). Also, if using an off-line copy of the OPE file for building the Emergency Disk, I would use the Microsoft.com copy instead for this build and wait out the download time.
Additional thoughts... this version now uses a base WIM (for Emergency Disk building) that is Win11-based (new from previous builds which always used a Win10-based WIM. There may be some issues here with your System but I don't believe there should be. If the above suggestions don't help, I can make a Win10-based OPE file available and you can do an off-line Emergency Disk build using that and try that one. I don't s'pect that the Win11-based Emergency Media should be a problem though...
