Page 1 of Bloody Windows update! Again!

Foolishly updated my PC last night and came back to a blue-screen brick this morning. Been running through every option today, but there's a little oddity stopping me from trying a couple of startup options.

In essence, once I select the startup recovery option and the PC soft reboots, my USB keyboard isn't activated so I can't choose any of the selections. I did manage to do it before as I ran a chkdsk via safe mode with command prompt.

Can't open up the bios either as I need to hit F2 during POST but the keyboard isn't switched on by then.

Quite vexing

============================
Writer`s Release

P/S 2 Keyboard?
Resetting BIOS by taking out CMOS Battery?

===========================
Jitendar Canth

Quote:
"I thought what I`d do was, I`d pretend I was one of those deaf-mutes."

Site Reviewer at DVD Reviewer & MyReviewer

Carving out a niche with a pneumatic drill at Anime @ MyReviewer.com

I have tried the CMOS battery thing (no jumper on the MB), but might not have left it out for long enough. I don't have a P/S2 keyboard, but I've got a whole bunch of peripherals I haven't thrown out so i might be able to blag something tomorrow.

============================
Writer`s Release

May need more info as none of the above relates to Windows.
What is the soft reboot mentioned?
I'm not aware of anything related to a Windows update that would cause an issue related to booting up to BIOS before Windows is invoked.

Ste

strange, as even old computers should let you use a usb keyboard for bios, if you hit cap lock on the keyboard does the light come on/are there any lights on keyboard when you turn it on?

what version of windows is it, not that that affects the other problem.

i've probably got 1 or 2 of those usb-ps2 converters somewhere, that i kept, "just in case".

edit - jsut realised, not ps2

do you have another keyboard you can try?

maybe pull out power completely for 5 mins and try again?

https://admars32.wordpress.com/
https://mobro.co/admars?mc=1

This item was edited on Sunday, 13th February 2022, 09:33

I've managed to resolve the bios problem. I removed the battery then spammed the F2 key while it was sorting itself out. Turns out USB optimization was enabled, which I presume is waiting for the full OS
to fire up before enabling the ports, which is annoying

Anyway, now I have some more options with regards to recovery/safe mode. Currently running a thorough chkdsk so I'll let you know how I get on.

Funnily enough, Luke's having a nightmare with Microsoft's enforcement system for the xbox (banned for no reason and nothing's showing up on their enforcement page). You'd think a company as big as this would be a little better at being able to maintain their own sh*t
============================
Writer`s Release

Right. Having some functionalilty in safe mode (which I'm using now, much more palatable that W7's SM).

I've tried to load up windows update but it's giving me an error message. If I try to load update history from the search bar the settings screen just vanishes.

Running sfc now, got a few more options after that. Best news is I've been able to backup some rather critical files regarding the Kid's EHCP & educational history so the biggest concern is resolved.

============================
Writer`s Release

there's a post where i had problems doing windows update and had to remove all files from various temp directtories, sfc, chkdsk etc

yes, good old, lets try a dozen things, hopefuly one will stick, may have been ccleaner, could have been a combo :(

https://www.myreviewer.com/Forums/PCs-and-Mobiles/t906084/Windows-7-RIP/page8

remember to delete from windows temp and user temp directtories



https://admars32.wordpress.com/
https://mobro.co/admars?mc=1

This item was edited on Sunday, 13th February 2022, 16:28

I've tried most of those, but I think it's beginning to look like my Windows Update service is damaged (makes sense). Can't uninstall updates, can't system restore. Trying to go straight into a subset of restore crashed the program

Running the troubleshooter. See how that goes

============================
Writer`s Release

Looks like KB5008876 is the culprit. Now I just have to get it off my machine

============================
Writer`s Release