Error Updating Windows 10 Pro X64.

[Formaleins]

Not sure if anyone can help with this one, it has me stumped so I am just seeing if anyone has the same problem or if they have managed to solve it. I am currently running the Windows Insider Program, my OS is running 1809, 18282-1000. 181109-1613. This has now been superseded by 1809-18290, which is the update I am trying to install. Everything else is up to date, Defender definitions etc. are all completed.

The update works fine and does the usual restart now and again up until it reaches 85% complete.

As soon as it gets to this point I get the Green Screen Freeze (previously the BSOD).  The error message is Kernel Security Check Failure.

Up to now I have tried the following, all with no improvement.

1: Disable the Kaspersky AV

2: Uninstall Gigabyte Autos Graphics Engine (has some issues with LED drivers which Gigabyte still hasn't fixed!)

3: Driver Verifier - flagged only one driver which has now been sorted.

4: SFC / Scannow runs with no issues.

5: CHKDSK again, completes with no errors

 

So, this is as far as I can go, I have run out of ideas as to where to go from this point - Any suggestions would be welcome.

 

Cheers.

[manarak]

you might try to scan the RAM for errors

[KneeDeep]

 

Just out of interest, why are you on the Insider Program? Are you testing?

 

The whole point of Pro, for me, it to block those annoying Feature Updates for as long as possible.

But here you are, testing for Microsoft and expecting us to troubleshoot a build that was released yesterday. ????

 

It's the Gigabyte Aorus Graphics Engine

 

My suggestion? Get off the Insider Ring if you cannot figure these things out for yourself or with the help of other Insiders.

There are known issues with the build. Why are you subjecting yourself to them?

 

https://betanews.com/2018/11/28/microsoft-releases-windows-10-19h1-build-18290/

 

[manarak]

36 minutes ago, KneeDeep said:

 

Just out of interest, why are you on the Insider Program? Are you testing?

 

The whole point of Pro, for me, it to block those annoying Feature Updates for as long as possible.

But here you are, testing for Microsoft and expecting us to troubleshoot a build that was released yesterday. ????

 

It's the Gigabyte Aorus Graphics Engine

 

My suggestion? Get off the Insider Ring if you cannot figure these things out for yourself or with the help of other Insiders.

There are known issues with the build. Why are you subjecting yourself to them?

 

https://betanews.com/2018/11/28/microsoft-releases-windows-10-19h1-build-18290/

 

 

I'm not an insider and I still get faulty Windows updates.

 

One thing I noticed just some days ago is that they broke file associations.

 

Control panel functions get deactivated one by one and users are told to use "settings" which usually offer only half the options.

 

Windows 10 updates also sometimes replace drivers without asking.

 

????

[KneeDeep]

24 minutes ago, manarak said:

 

I'm not an insider and I still get faulty Windows updates.

 

One thing I noticed just some days ago is that they broke file associations.

 

Control panel functions get deactivated one by one and users are told to use "settings" which usually offer only half the options.

 

Windows 10 updates also sometimes replace drivers without asking.

 

????

 

Windows 10 Pro; go into Setting and defer Feature Updates. You can install them six months later when they iron out the bugs.

 

Why would you update the whole OS every six months? What a PITA. Especially knowing that it will replace your dedicated Drivers with it own.

 

Edited November 29, 2018 by KneeDeep

[OneMoreFarang]

Often you can find lots of details in the Windows event viewer and in the log files.

The problem is that there are sometimes too many details and it takes forever to find out what went wrong.

I agree with above. You should only use the Insider if you are an expert and if you really want to be beta-tester for Microsoft.

I am pretty good with PCs and I was an official beta tester for Windows 3.1 a long time ago.

These days I prefer to run the standard version and leave the beta headache for other people...

Edited November 30, 2018 by OneMoreFarang
spelling

[Formaleins]

Normally (past year or so) the insider builds work fine, never had a problem before. Just subscribed out of curiosity, there are a load of new things that pop up in the new builds, new programs, some interesting new settings etc. Opting out of the preview build is not quite as easy as you might think. You need to opt out just at the right time - I missed it this time - Windows updated to this latest October build and the very next day, it had already updated to the April release. You then have to generally opt out there and then and put up with the preview you have now or you leave it and let it run it's course.

It is not always possible to revert to the final release.

Hey, Knee Deep - it is not a system update every 6 months, it is actually a complete reinstall of the latest OS Preview (FULL OS) every week to 10 days. So yes, every day is like Christmas.

I have Pro on my other machine and it is on the standard build, I just use this PC for overclocking and fiddling around.

 

I have uninstalled all of the things I could think of since the last update and nothing cures it. I guess I will just have to wait until the next iteration comes around in a week or two.

 

I was only hoping someone had seen this error before and knew what might be causing it.

 

Manarak, the memory on here has been scanned already using MEMTEST, I had to run that a couple of times when I received some faulty RAM from Corsair. It has been run twice without any errors when the new RAM turned up, so hoping it isn't that. 

My thinking is that it has to be a driver or some software that is being specifically loaded as the fault is not random. It fails at exactly the same place each time, 100% consistent. If there was a way to step through the process it would probably be detectable.

 

I'm just going to disconnect everything other than the main boot drive and my mouse and keyboard, uninstall all of my replaceable software and give it a run from there, see how it goes.

 

Thanks for the suggestions.

[Stocky]

40 minutes ago, Formaleins said:

So yes, every day is like Christmas.

...sounds like everyday's a potential nightmare to me.

[lungbing]

And you wonder why I am still on Windows 7.

[OneMoreFarang]

53 minutes ago, lungbing said:

And you wonder why I am still on Windows 7.

And you miss all the new security features of Windows 10...

The above post is about the free insider version of Windows 10. Some time ago that was called beta-version. And some time ago smart non-experts would never use beta-versions. Now some people think they can use free beta versions and then they are surprised if they don't work 100%. That's why they are called beta-version...