Recently I bought the relect 8 home 4 pack.

My system consists of>
MSI x58 pro-e (ms-7522)   i7 cpu 920 2.67ghhz, 24gb
1000gb crucial mx500, 500gb hitachi 7200rpm, 1500gb wd usb
 
Back panel usb connections- ms mouse, ms keyboard, hp printer, wd mass storage hdd.
I successfully created a full backup image of the crucial ssd. I then created the rescue disc using the suggested WindowsRE environment. The disc is created with a dvd/cd recorder. I utilized dvd-r media with a Lite-on ihas224. Testing the created disc was okay but no mouse or keyboard function exists.
However, after creating another disc with the same issue, I fooled around a bit and discover that unplugging and inserting the usb mouse cable enables mouse function of the rescue package. The same is true with the keyboard usb cable.
I have moved the two usb cables to different back panel ports individually (no device connected in the side by side ports).
USB legacy device is enabled in BIOS. Consistently, the rescue media works as described. And I get the mouse and keyboard function by removing and inserting the respective usb connector. Although it seems the recue media will function in a crisis, anything but a perfect boot with expected functionality is highly desired. Please help.

Let me add to the mystery>.
I installed Reflect 8 on my wife's computer.
ASUS p7p55d-e   i5 cpu 760 2.80ghz, 8gb
1000gb crucial mx500, 1000gb samsung 7200rpm, 1000gb wd usb
I successfully created a full backup image of the crucial ssd. I then created the rescue disc using the suggested WindowsRE environment. The disc is created with a dvd/cd recorder. I utilized dvd-r media with a Lite-on ihas224.
The rescue media works as expected with mouse and keyboard function. There is no need to touch back panel usb connections.

I am nearly 66 years old and have had some eye problems (retinal detachments and repairs) in both eyes. And other procedures required after detachments to get me back to best vision. My vision is good, but I may have missed something. I used to be a repair technician and supervisor building single board computers with passive backplanes. My first computer was a dx386 with dos 4.0. I used to run everything from dosshell and batch files. Things have changed.

Thank you for your time and input.

What version of Windows RE is actually in use?  That will be shown in the Rescue Media title bar running along the top of the interface.  Have you tried any other options, such as WinPE 11?  Some systems have WinRE partitions that have been customized in ways that can create driver conflicts when Reflect uses them as their baseline, including USB issues.  The WinPE options involve downloading components directly from Microsoft, which are then used without further customization before Reflect gets to those components, so it's a more consistent "foundation" to build from.  And as long as you don't need WiFi support in Rescue, you're not really giving anything up, apart from the storage necessary to cache those WinPE files.

+x

 

jphughan - 30 January 2023 7:48 PM

What version of Windows RE is actually in use?  That will be shown in the Rescue Media title bar running along the top of the interface.  Have you tried any other options, such as WinPE 11?  Some systems have WinRE partitions that have been customized in ways that can create driver conflicts when Reflect uses them as their baseline, including USB issues.  The WinPE options involve downloading components directly from Microsoft, which are then used without further customization before Reflect gets to those components, so it's a more consistent "foundation" to build from.  And as long as you don't need WiFi support in Rescue, you're not really giving anything up, apart from the storage necessary to cache those WinPE files.

Thank you.
The initial rescue disc is created with>
Windows RE ver. 2004 64bit
Macriun Relect Home 64bit 8.0.7175

Updated disc is created with>
PE 11 WIM build 22000 64bit
Macrium Reflect Home 64bit 8.0.7175

Testing this disc is successful enabling an operation mouse. Great!

I notice an anomaly in keyboard function. A press of alt+ F should highlight the File menu or underscore the F in file. There appears to be no keyboard function until the mouse has been clicked on something; all keyboard navigation is possible after the first mouse click.
It may normal rescue environment behavior but a little different that old the MS DOS editor.

Glad to hear that you’re all set. I do wonder what’s embedded in some people’s WinRE partitions that causes these USB driver conflicts, but I’ve never been in a position to deep dive on that, and trying to do that over a forum would be a bit tedious for both sides.

Interesting find on the keyboard shortcuts not being available until a mouse click. I wonder if that’s because the Reflect application window doesn’t have “focus” until it’s clicked on? But of course that’s a much easier issue to work around than non-functional peripherals.