Keyboard + mouse not functioning past BIOS following CPU+MB upgrade

To work with Windows 7 I recommend this keyboard and mouse kit

WARNING: The following will be a VERY long post as I exhaustively enumerate every step I've taken in my attempt to follow the advice provided by SIW2 and Megahertz07 to resolve my issue.

Preparatory Steps

1. To regain access to my Windows 7 operating system, I removed my SSD from my new hardware configuration and connected it to my old hardware. System booted up without issue and everything worked as it always has for the past 10 years.

2. I updated my ASUS TUF gaming B550-Plus motherboard's BIOS with the latest stable, non-beta version: AGESA V2 PI 1.2.0.1 Patch A (BIOS 2006). Actually I had already updated it previously; but I list it here in the interest of full transparency.

3. As detailed in my previous post, I've downloaded 1904v2.iso and - using Rufus - burned it to a FAT32 USB flash drive and made it bootable.

4. I've downloaded the driver patch files from Canonkong's post, extracted them, and copied them to the Uprograms > Drivers sub-folder of the 1904v2.iso directory of my USB flash drive.

5. Following SIW2's advice I've "...copy(ied) boot.wim from 1904v2.iso into the recovery folder and rename it winre.wim."

6. I've registered for my free O&O DiskImage 14 Professional license.

7. I've downloaded and installed O&O DiskImage 14 Professional on the SSD drive I'm attempting to make compatible with my new hardware, activating it with the free license I received.

8. Using O&O DiskImage 14 Professional I've made a backup image of my OS.

9. I then used O&O DiskImage 14 Professional to create a boot medium on a second FAT32 USB flash drive.

10. I then removed my SSD from my old hardware configuration and re-installed it to my new computer.

Steps Attempted to Boot the O&O DiskImage 14 Professional from the USB Flash Drive

I spent 8 hours yesterday adjusting, iterating, and testing BIOS settings in an attempt to get the USB flash drive to boot or otherwise get my SSD drive to boot under the new hardware configuration. I will not detail every combination of settings attempted. Rather, I will detail those which produced a result (whether positive or negative) while leaving out the redundancies.

NOTE: All "screenshots" are actually photos taken with a cellphone as I had no means of screenshotting my BIOS screens with an inoperable operating system. I did my best to make them clear enough to read. Apologies in advance for the poor quality.

Settings Universal to All Attempts





Scenario 1

Megahertz07 had advised to boot the USB flash drive as UEFI. My initial attempts focused on attempting to do just this.

1. In "BIOS > Boot > CSM (Compatibility Support Module) > Boot Device Control", I set it to "UEFI only".

2. In "BIOS > Boot > CSM (Compatibility Support Module) > Boot from Storage Devices", I set it to "UEFI only".



3. In "BIOS > Boot > Boot Option Priorities > Boot Option #1" I selected my USB flash drive inserted into a USB 2.0 port of the motherboard. In this scenario I chose the UEFI option but neglected to take a screenshot of it; I've inserted the text "UEFI" to the beginning of the option as it would have appeared in the drop down menu selection. To remove all variables, I disabled all other boot options.



4. After saving these settings and exiting BIOS, the computer reset. It went through POST but then stopped at the ASUS logo display screen, failing to boot the USB drive. This screen could only be exited through a Power Off, Reset, or CTRL+ALT+DELETE.



5. Scenario 1 = FAIL

Scenario 2

1. In "BIOS > Boot > CSM (Compatibility Support Module) > Boot Device Control", I set it to "UEFI and Legacy OPROM".

2. In "BIOS > Boot > CSM (Compatibility Support Module) > Boot from Storage Devices", I set it to "UEFI only".



3. In "BIOS > Boot > Boot Option Priorities > Boot Option #1" I selected my USB flash drive inserted into a USB 2.0 port of the motherboard. In this scenario I chose the UEFI option but neglected to take a screenshot of it; I've inserted the text "UEFI" to the beginning of the option as it would have appeared in the drop down menu selection. To remove all variables, I disabled all other boot options.



4. After saving these settings and exiting BIOS, the computer reset. It went through POST but then stopped at the ASUS logo display screen, failing to boot the USB drive. This screen could only be exited through a Power Off, Reset, or CTRL+ALT+DELETE.



5. Scenario 2 = FAIL

Scenario 3

1. In "BIOS > Boot > CSM (Compatibility Support Module) > Boot Device Control", I set it to "UEFI and Legacy OPROM".

2. In "BIOS > Boot > CSM (Compatibility Support Module) > Boot from Storage Devices", I set it to "Legacy only".



3. In "BIOS > Boot > Boot Option Priorities > Boot Option #1" I selected my USB flash drive inserted into a USB 2.0 port of the motherboard. As "Boot from Storage Devices" is set to "Legacy only" per #2 above, there is no option for choosing UEFI for the USB flash drive this time. Thus, it's simply "PNY USB 2.0 FD 8.07 (63.9GB)". To remove all variables, I disabled all other boot options.



4. On saving the BIOS settings and exiting, the USB flash drive boots, starting with a black and white screen with the text "Windows is loading files..." accompanied by a bar at the bottom of the screen measuring the progress.



5. A few seconds later the screen refreshes. A bar appears with a green tracking puck and the text "Microsoft Corporation" below it.



6. The screen refreshes again, next displaying the O&O DiskImage 14 Professional splash screen.



7. After a few seconds this is replaced with the O&O DiskImage 14 Professional End User License Agreement dialog box. Unfortunately, I experience the same problem which initiated this post to begin with; my mouse and keyboard become unresponsive. The computer accepts no input from either and I'm forced to either press the reset button or power off / power back on to exit this screen.



8. Scenario 3 = USB Flash Drive boots but computer fails to accept mouse and keyboard input. Unable to move past the O&O DiskImage 14 Professional EULA dialog box.

Scenario 4

1. In "BIOS > Boot > CSM (Compatibility Support Module) > Boot Device Control", I set it to "Legacy OPROM only".

2. In "BIOS > Boot > CSM (Compatibility Support Module) > Boot from Storage Devices", I set it to "UEFI only".



3. In "BIOS > Boot > Boot Option Priorities > Boot Option #1" I selected my USB flash drive inserted into a USB 2.0 port of the motherboard. As "Boot Device Control" is set to "Legacy OPROM only" per #1 above, there is no option for choosing UEFI for the USB flash drive this time. Thus, it's simply "PNY USB 2.0 FD 8.07 (63.9GB)". To remove all variables, I disabled all other boot options.



4. Scenario 4 = Results are the same as Scenario 3. The computer attempts to boot from the USB flash drive, gets through the O&O DiskImage 14 Professional splash screen, and then freezes on the EULA dialog box where it refuses to accept any input from mouse or keyboard.

Scenario 5

1. In "BIOS > Boot > CSM (Compatibility Support Module) > Boot Device Control", I set it to "UEFI and Legacy OPROM".

2. In "BIOS > Boot > CSM (Compatibility Support Module) > Boot from Storage Devices", I set it to "Legacy only".



3. In "BIOS > Boot > Boot Option Priorities > Boot Option #1" I selected my SATA Western Digital SSD this time. To remove all variables, I disabled all other boot options.



4. On saving the BIOS settings and exiting, the SATA SSD boots. A "Windows Error Recovery" window appears. I choose "Launch Startup Repair (recommended)".



5. After making the choice in #4, a screen appears displaying a light blue Windows logo followed by the text "Windows is loading files..." and a bar at the bottom of the screen measuring loading progress.



6. After a few moments this is replaced by Windows loading a Safe Mode / Repair Mode. Of special note is my mouse and keyboard work in this mode. At least that's some small progress.



7. I navigate to the USB flash drive on which I created the boot media for O&O DiskImage 14 Professional. Of special note is the GUI of Windows 7 has been replaced by a Windows 10 GUI. My assumption is this is the result of "...copying boot.wim from 1904v2.iso into the recovery folder and rename it winre.wim" way back in Preparatory Step #5 at the beginning of this post. So at least that worked :)



8. I then navigate to and double-click the oodipro.exe file to see if that will start up O&O DiskImage 14 Professional in the hope of running the "Adjust to new hardware feature" as instructed by SIW2. Unfortunately, I get an error message instead.



9. Scenario 5 = Able to boot into a Repair / Safe Mode of Windows and use mouse and keyboard. Unable to start up O&O DiskImage 14 Professional from my boot media USB flash drive to adjust to new hardware.

Scenario 6

1. In "BIOS > Boot > CSM (Compatibility Support Module) > Boot Device Control", I set it to "UEFI and Legacy OPROM".

2. In "BIOS > Boot > CSM (Compatibility Support Module) > Boot from Storage Devices", I set it to "Legacy only".



3. In "BIOS > Boot > Boot Option Priorities > Boot Option #1" I selected my SATA Western Digital SSD this time. To remove all variables, I disabled all other boot options.



4. On saving the BIOS settings and exiting, the SATA SSD boots. A "Windows Error Recovery" window appears. I choose "Start Windows Normally" (the screenshot shows "Launch Startup Repair (recommended)" highlighted, but I did choose "Start Windows Normally" in this instance).



5. Instant BSOD! Flashes for a split second then screen goes black.

6. Scenario 6 = FAIL.

Scenario 7

1. Less a test and more a question. I noticed in my BIOS' exit screen an option to "Launch EFI Shell from USB drives":



2. I clicked it once just to see what would happen. It gave me the following WARNING message:



3. I then examined the BIOS > Boot > Secure Boot options. Here are those screnshots:





4. I can't find an option to disable the Secure Boot state. It doesn't show in the screenshot, but it's a grey text entry rather than a white text entry indicating it's simply informing the user of a setting's state but which can not be clicked on to change. I was thinking if the Secure Boot state could be disabled, I'd then be able to test the "Launch EFI Shell from USB drives": BIOS exit option. Would this be worth pursuing? Thoughts, opinions, advice?

In Closing

Though some small progress was made in being able to enter a Windows Repair Mode / Safe Mode in Scenario 5 as well as have my mouse and keyboard work in that state, I'm still unable to get my mouse and keyboard to work with the USB flash drive boot media version of O&O DiskImage 14 Professional. Consequently, I'm unable to adjust my operating system to the new hardware as instructed by SIW2. Any suggestions on where to go from here?

On a whim, I attempted to boot from the USB flash drive to which I had burned 1904v2.iso.

The good news is it DID boot. It entered a Windows recovery/repair mode. The mouse and keyboard work. On the Desktop is a shortcut to the DISM++ app referenced in SIW2's previous posts.

I followed his instructions of selecting my operating system in the top pane and clicking "Open session".

I clicked "Drivers" in the left pane.

I clicked the ADD button at the bottom right and browsed to the sub-folder of the bootable USB flash drive where I had copied Canonkong's driver files.

It started the process.

However, I cancelled the task because it is out of sequence with SIW2's prior instructions to first use O&O DiskImage 14 Professional's "Adjust to new hardware" feature.

I just wanted to give an update on steps I've attempted and their results. It appears if the unresponsive mouse and keyboard issue can be resolved with regard to O&O DiskImage 14 Professional, then I should have no problem using DISM++ to install the drivers from the 1904v2.iso bootable USB flash drive.

So a small victory after yesterday's frustrating results.

SIW2 said:

Not sure it was a good idea to cancel halfway through installing drivers.

Hadn't planned to. Was expecting a confirmation screen before the process started with a "Continue" or "Cancel" button/option as is standard practice in pretty much every dialog box. Instead it started immediately after selecting the sub-folder where I'd copied the drivers. At which point I cancelled the task immediately.

I do have the backup image I made prior to starting this process to which I could restore if necessary.