Start PXE over IPv4
 

A couple of months ago my wife's older Lenovo PC did a Win10 update then died. No lights, no fans, no noises.

She wanted a new one anyway, so we got Lenovo from PCWorld. I brought it home, did the various Win10 setup palaver, then it said it had an update to do.

It did the update, rebooted then died. No lights, no fans, no noises.

I took it back to PCWorld and was told that many Lenovo PCs that had been bought in the last week had failed the same way.

It was exchanged and has worked fine ever since. I went back a couple of weeks later and was told that an update had wiped/corrupted the BIOS Eprom in almost every Lenovo PC they had sold over a few weeks. All over the UK.

Then last evening, it requested a reboot for a Windows update.

On reboot, it gave a message "Start PXE over iPv4". Then "Start PXE over iPv6". Then it shut down.

A bit of googling said that it needed attention to the boot sequence in BIOS.

I went in and it had been set to boot from a network via iPv4 then iPv6. No option to boot from the SSD, USB stick or DVD.

:confused:

I set it to the correct sequence (SSD then USB) and it now works fine.

What the **** is inside Windows updates these days? :confused:

Re: Start PXE over IPv4
 

It is a new and very very worrying "feature" that now MS seems to be pushing bios updates with windows update. This is an absolute crazy state of events as if something goes wrong then hardware can literally as you found out be bricked

I am hoping they do not start doing it for ATX etc motherboards and just OEM laptops and the like

---------- Post added at 15:33 ---------- Previous post was at 15:32 ----------

here is a report on it

https://windowsreport.com/bios-updat...indows-update/

Re: Start PXE over IPv4
 

Can't say I'm a fan of windows updates. Some photos from a few weeks ago after windows update did it's stuff. It screwed it and it screwed it good and proper. First it booted to an unreadable BSOD, then it wouldn't restore because the drive was corrupt then it gave up altogether.

It wasn't just reinstalling windows it was setting everything up and Plex forgetting what had been watched and what hadn't, Sonar wanting to re-download all the episodes you've watched and deleted etc. All with Mrs G asking how long until she can watch the latest episode of MasterChef USA or whatever she was waiting to watch. Nightmare.

Re: Start PXE over IPv4
 

Take yourself outside and give yourself a spanking hahaha

Backup backup backup. I keep monthly backupper images and take regular sonarr and radarr backups. My plex obviously is saved with the backupper image so at worst I would lost a week or 2

Re: Start PXE over IPv4
 

Disable updates and manage them manually, after everyone else has field tested them for you. Only pick the ones you need.

I have run that that way since W2000, its not really much of a task these days as W7 only releases Defender updates.