Windows Update when run is corrupting the MBR and laptop will not Boot

EdTittel said:

You can tell it's GPT/UEFI because the text in the window for the first partition reads "Healthy(EFI, System..." Only UEFI produces EFI partitions during install, and perforce that means the drive is GPT. You can't see that information on the General tab in the drive properties, but you can see it on the Volumes (which I don't see in your screencap, curiously enough):

Attachment 181113

FYI, GPT stands for GUID Partitition Table wherein the GUID Partition Table replaces the master boot record and its associated layout. Here's a further definition: GPT Definition from PC Magazine Encyclopedia. Furthermore, GUID is a Globally Unique IDentifier, a Microsoft method for identifying objects uniquely using 128-bit hexadecimal numbers. This MSDN document explains GUID Structure.

HTH,
--Ed--

Thanks for the explanation of the Three & Four Letter Abbreviations.

You didn't get to see the GUID on the screencap as it was not taken in the same place as yours.
When I went into File Explorer, then 'This PC' then 'Windows C Properties' and chose the 'Toshiba HDD' calling up the 'Properties of that and then under Volumes got it 'Populated' I got this:

I was suggesting imaging the efi parition as that may be the problem its worth a try if it goes just reimage that and see if it fixes it

EdTittel said:

OK, then: what comes next? I don't have the sense that we've defined a course of action just yet. Are you still experiencing the boot problem? If so, I would try performing some boot repairs. If you have a Macrium Rescue Media USB drive at your disposal, you could boot to that Windows image and use its excellent boot repair tool to see if that helps. Here's a link: Fix Boot Problems.
HTH,
--Ed--

Thanks, you read my mind as I was thinking the same thing as I wrote the last reply, but could not get the 'What comes next' under the image!

As I have currently 'Disabled' Windows Update in Local Services the laptop is behaving itself and starting up exceedingly well and keeping the Blood Pressure down!

Having said that I have Macrium V7.1 and used it on the last 2 Images I made of all the partitions (Except 'D') of the hard drive and that lot goes on an Ext HDD.
The 'D' which is my Data and is backed up separately also to the Ext HDD but to a separate partition.

Interestingly however I did try the 'Fix Start Up' feature of Macrium V7.1 after I used the Boot Up DVD to start the program and it failed to repair/fix the boot/start up, and that was when I thought 'bugger it' and restored the last image I made which was as the laptop started and just before Windows Update commenced identifying, downloading and installing all the files it identified as 'required' for the update.

Little bit nervous at the moment to reset Windows Update back to Manual or Automatic as I am a believer of 'If it ain't broke then don't fix it' and in this case more than likely for me 'screw it up again'!

But I still hope that a solution can be found that can repair this GUID GPT quickly to get back up and running with all the updates in place even though a number of them are not welcomed.

Cheers

Samuria said:

I was suggesting imaging the efi parition as that may be the problem its worth a try if it goes just reimage that and see if it fixes it

After spending about 6 hours today trying to carry out a Windows Update BUT before I did I made an Image of the EFI Partition using Macrium.
It failed to fix when reinstalled the start up of the laptop which repeatedly failed after Windows Update had spent a rather long time in downloading and installing the 18 Files it identified as being required.

topgundcp said:

Your HP Laptop came with Windows installed and the disk layout was customized by the HP manufacturer which included 3 Recovery Partitions, the first has the Recovery Environment, the second contains HP Diagnostic Tools and the one marked as OEM contains the Factory Windows Image. The EFI System partition (260MB) also contains special code for Push Button to enable you to restore the Laptop back to Factory, code for HP Diagnostic.

A fresh Windows Install will only have 4 partitions: 500MB Recovery partition, 100MB EFI System Partition, 16MB MSR partition and C drive.

Since You've already made the backup image using Macrium, you might want to re-arrange the partitions as shown above then try to update again. Note that by doing this, you will lose the ability to recover the factory image, however, I doubt if you ever need it unless you decide to sell the Laptop and want to put it back to the way it was which you can restore from the backup image.

FYI,

To use this 'Fix Start Up' feature. Since your Windows was installed using GPT disk layout, you MUST boot up the Rescue Disk with "UEFI mode"
look at the title of the screen shot, it should show what mode was used to boot.

Hi,
While I understand some of your reply, I must admit that my technical competence is not good enough to understand it all. however......
I did try using the Macrium Boot Up Disk for version 7.1 in UEFI Mode to 'Fix Start Up' but it didn't work after I spent the best part of today running Windows Update when 18 Updates were identified, downloaded and installed, but it took two attempts to get them, while the laptop would NOT start up after being 'Reconfigured'.

I only got going again by using 'System Restore' from the Advanced Recovery option which then deleted the 18 Updates from Windows.

So now 'Local Services' and 'Windows Update' has been reset to 'Disabled' as this has been a waste of a total day.
Sorry.

topgundcp said:

what version of Windows are you running now ? Just open Admin Command prompt and look at

Not quite the same 'display' but it's there below:

Windows 10.0.14393

1) What were the error messages and codes when you had attempted to upgrade from Windows 1607 to 1703 or Windows 1607 to 1709?

2) Open file explorer > this PC > C: > in the right upper corner search for:
a) supererr.log
b) setupact.log
This by default may be hidden so when using file explore you may need to click on view > check hidden items
3) Post the files into the thread using one drive or drop box share links

4) Run the beta version of the log collector and post a zip into this thread:
log collector v2-beta08.zip
(extract > open)

5) Please complete the steps in post #3