Updates Applied on March 13th or 14th Causing Major Issues? [ Problems with KB4088776? ]

Hello,

Yesterday I experienced major issues with 2 instances of Windows 10. They may be unrelated but the timing seems suspicious. Sorry that what follows is not a brief explanation [I'll do my best] but I think details count. I am posting this in case either the experience or the evidence I have is of use to anyone else seeing a similar issue.

I have a fairly powerful PC running 2 instances of Windows 10 Pro 64-Bit. I achieve this by virtue of having a 4-bay "docking unit" for 2.5" drives fitted in a 5.25" drive bay in the front of the computer. This allows me to put up to 4 2.5" SSDs in to the bay - each directly connected by SATA cable to the motherboard - and thus I can boot between different operating systems in the time it takes me to power down, swap drives and power back up again... This is relevant in what follows:-

I had my machine running a backup, copying some files to a spare physical HDD. Because the backup would take time, I left it running. When I returned, I noticed that one of my 3 connected monitors had "gone dark". As far as my nVidia Control Panel was concerned, the "dead" monitor had suddenly stopped being a "Dell U2415" and had become a "Generic Monitor" [how?] and was no longer visible to the OS and had gone idle and dropped in to power-save state. When the backup finished, I rebooted the machine, but the monitor did not reactivate.

I powered down this image of Windows 10 [my "Office" build], removed the 2 SSDs and fitted the 2 drives that make up my "Gaming" build. Powering up, I was unable to get *anything* to display on *any* of my three monitors. [ I have an nVidia 1080GTX GPU and connect my 3 monitors using the DVI-D port, an HDMI Port and a DisplayPort on the GPU]. I could see that the machine had booted from the drive activity light; I was able to type in my password and hear the "Windows Logon" audio cue, so I know the OS booted; however the monitors remained dark.

Returning to the "Office" build, and using the USB Key I was sent when I purchased my Windows 10 OS, I rebooted the PC, used the USB Key to get to Repair Mode, then used the Restore function to roll back to the most recent checkpoint. This proved sufficient to restore the Gaming build to operational use [although I've never before needed to use this functionality]. Upon closer checking, I see that it had applied update KB4088776 and that my repair had apparently reversed out that update.

Encouraged, I then swapped drives back to my "Office" build and attempted the same procedure. This time, however, I was unsuccessful. I received an error message to the effect that the repair process could not "see" a Windows OS to restore to.

OK. I reverted back to my "working" gaming image, then put the "C:" drive [SSD] from the dead "Office" build into my eSATA dock to explore. I found what looked to be an entirely reasonable drive present. I ran a chkdsk and all appeared OK. However, I did notice that I had both a "Windows" folder and a "Windows.old" folder. The "old" folder had a single directory path down a couple of levels and then I think one file remaining...

However, on the "System Reserved Partition" [the 500Mb partition that is created by W10's installer] I found a folder, "Temp", which are listed with their contents at the foot of this post.

Try as I might, I was simply unable to recover the second machine; it consistently refused to boot and instead gave me the W10 equivalent of a blue screen each time I tried. In the end, I ran Samsung SSD checks against both the C: and D: drives from the office build, then re-installed Windows 10 and spent most of yesterday re-installing all my business applications.

I cannot explain why I observed different results from 2 builds which should have been identical in pretty much all respects apart from 2: each had a unique software configuration (one was virtually all games, one had Office 2016 Pro, Photoshop, Lightroom, and a bunch of other office/photography related packages on it. Each OS build was made from a pair of drives: each used a 256Gb Samsung 850 Pro as the "C" drive; the Gaming build uses a 1Tb 850 Pro as a "D" Drive; the Office build uses a 512Gb version. The gaming build uses nVidia's software utility to turn my three 1920x1200 monitors into a single 5760x1200 logical display [to be games friendly]; the office build didn't need to do that.

I don't believe in coincidence: it might be unusual to expect a Windows update to corrupt a drive partition table, but it looks for all the world as though it happened here...

I've never seen Windows trash one of my PCs so comprehensively before and I'm a bit worried that another "invisible" update might cause more damage. Can anyone tell me if anything shared here is appearing elsewhere?

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Files from the "Temp" Folder on the System Reserved Partition of the "Office" build.

bcdinfo.txt

bootfailure.txt

disklayout.txt

SrtTrail.log

SrtTrail.txt

File contents were:-

bdfinfo.txt

The boot configuration data store could not be opened.

The requested system device cannot be found.

bootfailure.txt

{contains some invalid characters} - looks to be a total of 3 characters, Hex &00, &00, &00 - but I might be wrong

disklayout.txt
Microsoft DiskPart version 10.0.10586
 
Copyright (C) 1999-2013 Microsoft Corporation.
On computer: MININT-JAUAU45
 
  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          238 GB  1024 KB          
  Disk 1    Online          476 GB      0 B        *
  Disk 2    No Media           0 B      0 B          
  Disk 3    No Media           0 B      0 B          
  Disk 4    No Media           0 B      0 B          
  Disk 5    No Media           0 B      0 B          
  Disk 6    No Media           0 B      0 B          
  Disk 7    No Media           0 B      0 B          
  Disk 8    No Media           0 B      0 B          
 
Disk 0 is now the selected disk.
 
Samsung SSD 850 PRO 256GB
Disk ID: 14B77571
Type   : SATA
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(1F02)#ATA(C00T00L00)
Current Read-only State : No
Read-only  : No
Boot Disk  : No
Pagefile Disk  : No
Hibernation File Disk  : No
Crashdump Disk  : No
Clustered Disk  : No
 
  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 2     C   System Rese  NTFS   Partition    500 MB  Healthy             
  Volume 3     E                NTFS   Partition    237 GB  Healthy             
  Volume 4     F                NTFS   Partition    473 MB  Healthy    Hidden   
 
  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     N                       DVD-ROM         0 B  No Media            
  Volume 1     O                       DVD-ROM         0 B  No Media            
  Volume 2     C   System Rese  NTFS   Partition    500 MB  Healthy             
  Volume 3     E                NTFS   Partition    237 GB  Healthy             
  Volume 4     F                NTFS   Partition    473 MB  Healthy    Hidden   
  Volume 5     D   Apps         NTFS   Partition    476 GB  Healthy             
  Volume 6     G                       Removable       0 B  No Media            
  Volume 7     H                       Removable       0 B  No Media            
  Volume 8     I                       Removable       0 B  No Media            
  Volume 9     J                       Removable       0 B  No Media            
  Volume 10    K                       Removable       0 B  No Media            
  Volume 11    L                       Removable       0 B  No Media            
  Volume 12    M                       Removable       0 B  No Media            
 
Volume 1 is the selected volume.
 
There are no disks attached to this volume.
 
Read-only              : No
Hidden                 : No
No Default Drive Letter: No
Shadow Copy            : No
Offline                : No
BitLocker Encrypted    : No
Installable            : No
 
Virtual Disk Service error:
There is no media in the device.

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

SrtTail.txt

 
Microsoft DiskPart version 10.0.10586
 
Copyright (C) 1999-2013 Microsoft Corporation.
On computer: MININT-JAUAU45
 
  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online          238 GB  1024 KB          
  Disk 1    Online          476 GB      0 B        *
  Disk 2    No Media           0 B      0 B          
  Disk 3    No Media           0 B      0 B          
  Disk 4    No Media           0 B      0 B          
  Disk 5    No Media           0 B      0 B          
  Disk 6    No Media           0 B      0 B          
  Disk 7    No Media           0 B      0 B          
  Disk 8    No Media           0 B      0 B          
 
Disk 0 is now the selected disk.
 
Samsung SSD 850 PRO 256GB
Disk ID: 14B77571
Type   : SATA
Status : Online
Path   : 0
Target : 0
LUN ID : 0
Location Path : PCIROOT(0)#PCI(1F02)#ATA(C00T00L00)
Current Read-only State : No
Read-only  : No
Boot Disk  : No
Pagefile Disk  : No
Hibernation File Disk  : No
Crashdump Disk  : No
Clustered Disk  : No
 
  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 2     C   System Rese  NTFS   Partition    500 MB  Healthy             
  Volume 3     E                NTFS   Partition    237 GB  Healthy             
  Volume 4     F                NTFS   Partition    473 MB  Healthy    Hidden   
 
  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     N                       DVD-ROM         0 B  No Media            
  Volume 1     O                       DVD-ROM         0 B  No Media            
  Volume 2     C   System Rese  NTFS   Partition    500 MB  Healthy             
  Volume 3     E                NTFS   Partition    237 GB  Healthy             
  Volume 4     F                NTFS   Partition    473 MB  Healthy    Hidden   
  Volume 5     D   Apps         NTFS   Partition    476 GB  Healthy             
  Volume 6     G                       Removable       0 B  No Media            
  Volume 7     H                       Removable       0 B  No Media            
  Volume 8     I                       Removable       0 B  No Media            
  Volume 9     J                       Removable       0 B  No Media            
  Volume 10    K                       Removable       0 B  No Media            
  Volume 11    L                       Removable       0 B  No Media            
  Volume 12    M                       Removable       0 B  No Media            
 
Volume 1 is the selected volume.
 
There are no disks attached to this volume.
 
Read-only              : No
Hidden                 : No
No Default Drive Letter: No
Shadow Copy            : No
Offline                : No
BitLocker Encrypted    : No
Installable            : No
 
Virtual Disk Service error:
There is no media in the device.

 

Question Info


Last updated July 12, 2018 Views 105 Applies to:
Hi Bunny. I'm Greg, an installation specialist and 8 year Windows MVP, here to help you.

For the first drive, assure your System Restore is turned on and a point is set, then observe if the Update fails again and if so roll back either the Update in Settings > Update & Security > Windows Update > Installed Update History or System Restore, immediately check for and block it with Hide Updates Tool: https://www.howtogeek.com/224471/how-to-prevent...

The other drive sounds like it corrupted beyond repair, even as it was trying to archive the old install which it would only do on an Update if it couldn't start. Otherwise, had it recently Upgraded to Fall Creators Update Version 1709? It only keeps Windows.old for 10 days before Disk Cleanup automates deleting it.

What I would do is test the drive with bootable long test here: http://blog.nowherelan.com/2013/04/04/boot-seat...

Then do a full Disk check: https://www.groovypost.com/howto/check-hard-dri...

After the drive checks out, wipe all partitions to do this Clean Install which compiles the best install possible that will stay that way as long as you stick with the tools and methods given: http://answers.microsoft.com/en-us/windows/wiki...

Remember to keep the other drive unplugged unless you want to configure a Windows Dual Boot Menu that will make the latest install not be able to boot on it's own until it has the boot manager moved to it. It's cleaner to boot your choice via the BIOS Boot menu.

I'm sorry you went through this, but at this point we're just trying to keep customers afloat with all of the Windows Update failures. If you want to express your opinion on this to Microsoft use the Feedback Hub app in Start Menu where developers are tasked to process consumer feedback. They will not even see it here. This is a tech forums staffed mostly by volunteers trying to help others with your problems.

I hope this helps. Feel free to ask back any questions and let us know how it goes. I will keep working with you until it's resolved.
----------------------------------
I am a volunteer and not Microsoft.

Over 100,000 helped in forums for 10 years. I don't quit for those who are polite and cooperative.

Windows MVP 2010-19

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Hello Greg,

Firstly, thanks so much for a prompt and helpful response.

I will follow the guidance you've offered and report back. I'm a little cautious with respect to the '776 update, since it is huge - it is the latest Cumulative update for W10... However, I think it's important that I check that the image is correctly set for System Restores...

As to the second drive - well, my conclusion was the same as yours. Unfortunately, I needed that image to be working straight away, so I did the only thing I could, which was to wipe the drives, test them and then re-install Windows and all my Application software. I've re-used both drives [they were all I had to hand at the time] although I do agree that more extensive disk checks would be sensible.

Just looking at the options you offer me - the "bootable long test" and the "Full Disk Check" - and bearing in mind that I've since wiped, reformatted and re-installed over the top of the volume - can you comment on whether either/both of these tests would be "safe" with what is hopefully a now-rebuilt machine? [ I'd hate to cause further trouble through testing].

This is mostly unrelated, but I spent a lot of time over my end-year break trying to get a brand new machine to work properly - in that case it turned out that it was the latest major update [Fall or Creator's Edition?] that had a weird conflict with my Firewall of choice that was causing the Start Menu to break... I mention it here only in the context of the observation that it seems as though [in my limited experience] this has been a buggy, unreliable release. I know we need to keep up-to-date, especially to address vulnerabilities, but reliability of W10 is starting to look suspect.

Let's hope things go quiet again...

Thank you for your kind assistance...

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I know of no way that doing the disk diagnostics and Disk Check would mess up your PC build. If the disk is failing you need to know this anyway, and a Disk Check can always lost data in a bad sector if it finds and tries to repair it. This is why it's always important to have the data and a System Image backed up.

If you have not yet done the Clean Install in this link then be aware that no one who has followed that tutorial has come back to report a single issue, not any of the half million who have completed it in Windows 10, or the 2+ million who did the same install in Windows 7: http://answers.microsoft.com/en-us/windows/wiki...

This is why I always say that "the install is everything."
----------------------------------
I am a volunteer and not Microsoft.

Over 100,000 helped in forums for 10 years. I don't quit for those who are polite and cooperative.

Windows MVP 2010-19

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Greg,

Today I switched on the "Office" build of my PC [which I rebuilt from scratch Wednesday] and the machine was working perfetly. I used it for about 2 hours and had zero issues...

I left the machine running [copying some files to my NAS] whilst I went to get some lunch. On my return, I discovered that, once again, the "left" of my three monitors had become disabled, again.

The machine itself looked OK this time. I checked Control Panel > Security and Maintenance and I see that the "last run date" for Automatic Maintenance was today at 12:22, which coincides with the time I was away from the machine. When I check the update history, however, I see that 2 Quality updates were applied on March 14th [ KB4088785 and KB4088776] and an "Other Update" was installed at the same time [KB890830]. All updates were apparently successful.

When I check my nVidia details [which I have not touched since the clean rebuild on Wednesday] I discover that the machine is running a very out-dated version of the nVidia driver... I had previously downloaded the latest [391.01] so I have installed that latest driver. This update ran perfectly smoothly, but, once again, the left-most monitor remains dark... I've checked the cables [OK as far as I can tell]. If I run up a copy of Mint Linux on this hardware, then using the Nouvea driver, all three screens work flawlessly.

I've tried both rebooting and full power-off/power-on resets of the system both before and after application of the latest nVidia driver - neither of which made the slightest bit of difference.

I can see no explanation or justification for what is happening. If the monitor had been consistently dead, I would suspect the monitor or the cable; but it was working perfectly until I went to lunch. I've now tried a raft of obvious things to restore the monitor to a working state, but it is consistently refusing to work. I know that the nVidia software configuration has been stable [either side of the update I explicitly performed] so I don't think that's the cause.

Which leaves Windows. According to my system's own W10 log, a System Update was run at 12:22, even though there is no evidence of explicit change being made.

Can you suggest any possible reason why this would cause what looks to be a permanent refusal to recognise this monitor?

I'm completely stumped...

Thank you

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Greg,

Just to give a more complete picture, I have just swapped my boot drives and loaded up my gaming build. As I originally mentioned, there is a small software configuration difference between the two systems, because the gaming build merges all 3 displays at the driver layer to create a single virtual desktop of 5760x1200 resolution, which is easier for games to cope with.

The gaming rig is giving me all three displays, perfectly...

Below is an image of what I see in nVidia Control Panel on the Gaming system. The crucial point here being that this is the *exact same* hardware configuration, with the same cables, ports and sockets being used for both Gaming and Office builds. In other words, this is not likely to be a hardware problem.

I checked the nVidia driver version for the Gaming system and that's 388.71 - not quite up to the 391.01 now on the Office build, but only I think one or two releases back. However, I still think the crucial point here is that one of my three monitors "turned itself off" when I was simply away from the computer...

Any thoughts?

Thanks for your continued interest on this - it's driving me round the bend...

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

OK...

Now this gets utterly weird. Having tested and validated that the Gaming build is still OK, I've powered that down, swapped the discs again and booted back to the office build, to see if I can harvest any activity data.

In the nVidia Control panel, I could still see the three radia-button-selector buttons for my three monitors, with the last one being deselected. Out of pure random chance, I clicked on the empty selection box, and... it "took".

OK, so the monitor came back to me in the wrong virtual location, but a quick drag-and-drop sorted that...

I haven't yet dug back in to the logs to see what if anything has changed, but this is utterly, utterly weird. And please don't take this the wrong way, but as a platform, Windows 10 is making life much harder when it comes to diagnosing and triaging this sort of thing. Finding actionable evidence of misconfigurations is virtually impossible; finding an actual breadcrumb trail that actually explains this weirdness is totally impossible.

Windows needs to do a much better job of providing useful diagnostic help to people.

I hope this might be the last of it... but will report back if things go weird again.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Sounds good. Keep us posted.

I miss Windows 7 which I cut my teeth in the forums supporting and was a piece of cake by comparison. We're just trying to keep customers afloat here with hardly any time (we're volunteers) to pull together Best Practices or troubleshooting regimens - before the next disaster strikes!

If you want to express your opinion on this to Microsoft use the Feedback Hub app in Start Menu where developers are tasked to process consumer feedback. They will not even see it here. This is a tech forums staffed mostly by volunteers trying to help others with your problems.

You can post back here the Feedback Share link and I'll try to vote it up with my MVP badge FWIW.
----------------------------------
I am a volunteer and not Microsoft.

Over 100,000 helped in forums for 10 years. I don't quit for those who are polite and cooperative.

Windows MVP 2010-19

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Thank you for the suggestion to use the Feedback Hub - I will do that. Although I don't know the root cause, all the evidence I have points to this being related to Windows Update, so I'll offer that back to MS.

If nothing else, I would like them to understand the "cost" of this... Not only has it taken some of your time, but my principle "earning" machine was off line for a day - so that's a day without income for me. The full and total loss of the office build also meant that I was unable to "uninstall" a whole host of licensed software, including

Adobe Photoshop and Lightroom

Microsoft Office 2016

Omnipage OCR

etc, etc

My attempt to re-install the Omnipage was rejected by the software, claiming license limitations, because that was the third time I had installed the package. I'm now negotiating with the vendor to see if they will be willing to unlock my software - and that's still unresolved. This is the aspect of the issue that I'd like MS to understand - the downstream consequences of this sort of failure.

Thank you very much for your support.


Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.