Win10 1709 (ent) - NTFS,55 Errors after (cumul) Updates

[win10hugo]

Hello,

in our environment with over 500 devices we have a very frustrating problem:

After installing Cumul. MS-Patches like KB4499147 through WSUS or any other Cumul. Patch we get contantly get errors with Event ID 55, Source NTFS. This leads to devices not finding their domain, black monitor screens and all kinds of problems. The only help we know is
chkdsk /f C:
That helps. But only until the next update.

The really frustrating part is that these ntfs,55 error come after a few days. We are watching the event logs after updates very closely. Very often nothing happens (with many reboots and shutdowns) then one day you get a call and the problems mentioned above and you have to run chkdsk.

What we already did:

• sfc /scannow
• dism /online /cleanup-image /restorehealth
• disable vss service because event logs where telling us that there is not enough space for the shadow copies and soon after that we would get ntfs,55
• turn off hibernate

Now we are at a point that Patching our Windows 10 machines is just one very big headache and we have no idea how to proceed. What we know is, if we get ntf,55 and run chkdsk everything is find as long as we do not install any windows patches (office is ok).

Perhaps important: All the machines are installed with an image that has an customized ISO (deinstalled apps through dism) which was installed in a VM where in Audit Mode Office and Windows Updates was installed. All finalized with a sysprep.

Can anyone help on this?
Hugo

 

[Tim Locke]

Windows 1709 is pretty ancient . Is there a reason that you cant move to 1903 and test all your apps with it and then roll it out. Which I realize will be a big job.

 

[Wolfie]

See also:

https://www.windows10forums.com/threads/how-to-upgrade-windows-10-to-the-latest-version.13015/

 

[win10hugo]

Hello,
thx for the answer and the link.

I was hoping for a more specific answer on our problem. For various reasons we don't want to migrate and have to solve the issue for 1709.
Perhaps someone can help with our problem?

 

[Wolfie]

Hi win10hugo,

if you are running 1709, it may well be that it just isn't up-to-date enough and I can really only recommend that you update to the current version (1903).

Look on MS's support pages for more info:

https://support.microsoft.com/en-us/help/10064/set-up-your-small-business-network

I don't have anything else for you really!.