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

[SIW2]

Rt click the extracted Windows folder and select add to archive




Select wim in the dropdown




Click the button and browse to boot.wim




Click OK

 

[SIW2]

All done:

 

[Upgrade Help]

Assuming the O&O boot.wim was created from 1904v2 ( I suspect from your screenshots, that win7 winre.wim was used - because the bootmgr and bootmgr efi files are the size expected from win7 winre. That also explains the microsoft loading bar )

Thank you for the quick response and helpful advice.

Here's what I'm not clear on:

I took your original post on this subject...

Little cheat to create O&O boot media from win7

Rename your win7 winre.wim , and copy win10 winre.wim into the win 7 recovery folder, like this:

View attachment 413700

OR copy boot.wim from 1904v2.iso into the recovery folder and rename it winre.wim

...to mean that - prior to making the O&O boot media - I was to copy the boot.wim from 1904v2.iso into the recovery folder on the C: drive of my SSD and rename it winre.wim. Was that correct? Because that's what I did.

If, instead, it needs to be copied to the O&O bootable USB flash drive, I don't see a "recovery" folder there into which to copy it. I only see a "boot.wim" inside the "sources" folder.

 

[SIW2]

copy the boot.wim from 1904v2.iso into the recovery folder on the C: drive of my SSD and rename it winre.wim.

Win7 winre.wim will be in a folder called recovery\{some_long_number}

Yes, effectively replace windows7 winre.wim with 1904v2 boot.wim ( renamed to winre.wim ).

It seems to be in the right place because winre.wim is booted when you use the launch repair option.


So it is odd that apparently your O&O media has smaller bootmgr and bootmgr.efi files


Check the size of boot.wim on your O&O usb stick.


Check in the windows\temp folder and see if there is anything there.

 

[Upgrade Help]

After having a night to sleep on it, I've considered that maybe I'm overthinking this. I have a family member with a Windows 10-based system.

I installed the licensed version onto my Windows 7 SSD. However, it appears O&O has a 30-day free trial period. So could I just use the trial version to make the bootable USB on the family member's Win 10 system? Then there's no need to worry about copying boot.wim from 1904v2.iso, renaming it, making sure it's in the correct folder, etc.?

Would that work? Or does the bootable USB have to be made from the HD/SSD to which the "Adapt to new hardware" module will be applied?

 

[SIW2]

So could I just use the trial version to make the bootable USB on the family member's Win 10 system?

yes

 

[Upgrade Help]

Latest progress:

1) Created the bootable O&O DiskImage 14 Professional USB flash drive using a family member's Windows 10 computer.

2) Inserted the bootable USB flash drive into my own computer and successfully booted into/accessed O&O.

3) Ran the adjust to new hardware module following your previous instructions. No issues or difficulties.

4) Shut down my computer, removed the O&O USB flash drive, inserted the 1904v2.iso/DIMM++ bootable USB flash drive, powered on my computer, and booted into/accessed this second USB.

5) Ran DISM++ per your previous instructions to install Canonkong's driver files.

6) Received message: Operation succeeded. Success 43, not applicable 0. Refer to "Config\DISM++.log for more information.

7) Clicked "OK" to close the message box, exited DISM++, ejected the USB flash drive, and restarted the computer.

8) The "Windows Error Recovery" screen comes up.

9) I choose "Launch Startup Repair (recommended)".

10) The "Windows is loading files..." window appears.

11) The Desktop appears in the minimalist Repair Mode.

12) I restart the computer, the "Windows Error Recovery" screen comes up again, and I choose "Start Windows Normally" this time.

13) Instant BSOD ! But - unlike previous BSODs - this one persists rather than flashing across the screen for only a fraction of a second before going black.

14) Power computer off and back on again.

15) The "Windows Error Recovery" screen comes up again.

16) I choose "Launch Startup Repair (recommended)" again.

17) After the "Windows is loading files..." window finishes, it's replaced with a black screen and a wite mouse cursor.

18) I can move the cursor. It disappears if moved to the bottom of the screen; as if it's passing behind an invisible / black Windows task bar. I can recover it/make it reappear by simply moving the mouse cursor back up the screen.

19) CTRL+ALT+DELETE brings p a visible Task Manager window.

20) After a few minutes of black screen, the desktop spontaneously appears/becomes visible again. It is in minimalist Repair Mode.

21) I can use the mouse and keyboard. I can open Explorer. I can see my local disk as drive D: instead of the usual drive C: I can see all of my old folders and files on the D: drive.



22) A restart returns to "Windows Error Recovery Screen" again.

23) I choose "Start Windows Normally" this time, which again results in an instant BSOD.

24) Power off and back on.

25) A return to "Windows Error Recovery Screen" again.

26) I choose "Launch Startup Repair (recommended)" for the third time.

27) The black screen and white mouse cursor appear again.

28) Somewhere between 3 to 5 minutes the Desktop reappears again as it did in step 20. It's still in minimalist Repair Mode, my primary drive which was previously labeled C: is still labeled D:, I can use the mouse and keyboard, navigate Explorer, etc.

Though this represents progress over the previous few days, I'm stuck at this point. I can't seem to get Windows to start normally; it just goes straight to a BSOD. At a loss as to where to go from here.

 

[kapqa]

YES




You can put them there if you like. They can be anywhere that can be seen from the booted media.





In dism++ select the target os by clicking it in the top pane to highlight it in blue.
Then click open session.
Then click Drivers in the left pane.
Then click the ADD button at bottom right and browse to the FOLDER containing the extracted drivers

-is it enough to click "ADD" button to make the changes to the local windows installation disk or must there be another change, like "save image" or similar?

-must one run O&O (add new hardware layer) tool once more after a failed attempt before running dism++ again?


my problem is not having any USB anymore on stx-board a300 after upgrading CPU from A-Series to Picasso.
Even after adding the AMD Driver with the method above, there is no usb driver loaded, and the mobo has no chance to use ps/2.

- - - Updated - - -

all my windows 7 on ryzen system run in CSM mode only; maybe others have made to run it in UEFI; if i change processor, have to enable it CSM again, because for some reason it gets disabled.