Stopping the 'Blue Screen' from 'popping up' for Win 10 'invasion'!

CountMike said:

I can only answer to what's addressed to me.
"So are you saying that XP Pro which also has SP3 installed on my machine, is not an OS?" No idea what you surmised that from what I wrote ? It's just an old OS without official support for long time now. Comparing to newer Windows it's woefully insecure even with other security programs/AVs installed.
Still works beautifully though, and NO reported issues!
"Using 1607 has not presented any security issues over the last 12 months, and has not caused anything to stop working, except for this dam ‘Blue Screen’. ". You probably just never noticed what may have happened. Just one example: Meltdown and Spectre it's solved only by regular updates and on HW (microcode) level.
These 2 'problems' were reported in the National & International Press and were 'repaired' with an update which I obtained in January 2018.

​Replies in BLUE Text above.

To BunnyJ

Setting Internet to Metered and also using WiFi did not stop the appearance of the Blue Screen, but then BIG BROTHER still likes to try and keep you 'PARANOID!!!'

To Bree:

Found the KB4091461 and this has been Uninstalled now, so will see what happens over the next few days and post a 'progress report'

Thank you for the pointer, it was appreciated.

Progress Report:

Removal of KB4091461 worked and Blue Screen has been stopped.

I have also used WUMT and updated OS v1607 with a number of what Microsoft call 'Critical Updates' as well a number that were for Microsoft Office.

Thanks for the answer/solution 'Bree'.

Bree said:

Glad to have helped.
While I respect your choice to stick on 1607, I still think you should consider an upgrade to a newer version like 1709 for security reasons. 1607 will not get any more security updates now it's past end of support.
Should you wish to try, first make a system image and the associated recovery boot usb with something like Macrium Reflect (free). Then you can always return to your current system should it not work out.

Hi Bree,

I looked at 1709 and found it was a download of 3.41Gb while when I just downloaded it using WUMT the file was just 24.92Mb, which seemed a bit strange!
So we will see what happens when the install takes place.

While Macrium is firmly fixed to my right hand and is invoked after every successful update when the PC is booted up and found to be fully functional and not 'mortally wounded' as it seems a lot of users have found with certain updates from Microsoft.

Needless to say Macrium Restore has been called into action on a number of occasions and has worked exceptionally well on every occasion!

Cheers and 'Fingers crossed' for the next step!

****UPDATE****

Well the 'Fingers Crossed' didn't work as the Download/Install of the 24.92Mb File 'Failed' so now it has switched back to a 3.39Gb Download/Install!

Looks like we are in for a long night! Arrrgh!

Bree said:

The 'Features update to Windows 10, version 1709' seems to be a small file, the purpose of which is to kick off windows update to download the rest of the install files in the background. 3.41GB sounds the right size for that,
I always do my upgrades manually by downloading the install media to an ISO or (my preference) a USB using Microsoft's Media Creation Tool.
Download Windows 10 ISO File
To start the upgrade mount the ISO or plug in the USB then, in your current Windows, use File Explorer to find Setup.exe on the root of the drive and run it. That is what I may well be doing on Tuesday if/when 1803 is released (if the rumours turn out to be true).

Hi Bree,

Just before I got your reply I had already started the update using the WUMT program to get the 3.41Gb of 'program'.

In total the PC has spent around 8 Hours today , downloading, installing and configuring the 'Update' to 1709, except that...........

When I booted the PC after the 'configuration' had completed and I logged in, going into 'System' to find the OS, I am still on 1607!!! There were no error messages at any stage of the now wasted time.

So I guess I can join the ranks of users with failed updates!

I wish you 'Good Luck' for the coming week and 1803.

Bree said:

Not necessarily. There's no need to use third party tools to upgrade, particularly if they don't report errors properly. In fact, I can't recall seeing any posts on TenForums saying they had used WUMT to perform an upgrade. As I said...
Should that way of upgrading fail a full error code will be reported identifying the problem encountered. There are plenty of people on TenForums that can provide a solution, given that error code.
Not that it's likely to fail, general consensus on these boards is that a manual upgrade is the most reliable method, often succeeding where letting Windows Update perform the upgrade had failed.

OK.
Having now got the Windows 10 ISO File can you possibly remember how long the installation and configuration took in total please? (Ball park time would be OK)

I just don't want to start this at night and find I am still here at 04:00hrs in the morning!

Also having Windows Updates, and UpdateOrchestrator currently 'Disabled' will not cause any 'problems' carrying out the upgrade manually?

Cheers