Windows 10 Announced - Released 29-Jul-2015

Several minutes.. long enough to know I was shafted..

 

After upgrading to 1803, here's what I have encountered so far:

1. First cold boot after upgrade, a blue screen stating Windows was unrepairable. Ignored it and rebooted and all was fine.

2. After the May cumulative update, another blue screen with some nonsense text. Ignored it and rebooted and all was fine.

3. A couple days after May cumulative update not only would the PC not boot, it wouldn't power on! That one had me worried. Tried everything to get power to the PC. Finally "wiggled" power cord connection to the power supply. That did the trick. PC booted and was fine afterwards.

4. For the "coup de gras" and latest incident after recently applying KB4100403 cumulative update, I reviewed my Reliability History in Control Panel on next cold boot after the update was applied. It states in bold under Critical Events - Windows - Hardware Error:

Date - 5/25/2018 7:42 AM

Status - Not reported

Description

A problem with your hardware caused Windows to stop working correctly.

Problem signature

Problem Event Name: LiveKernelEvent
Code: ab
Parameter 1: 1
Parameter 2: 80
Parameter 3: 0
Parameter 4: 4
OS version: 10_0_17134
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.17134.2.0.0.768.101
Locale ID: 1033​

First, the PC booted fine so had no inkling that this was detected. Next, thoroughly searched the Windows event logs for any reference to this. Zip references found. BTW - PC today cold booted w/o the above entry.

Bottom line - I am convinced Microsoft's gross incompetence "knows no limits" anymore. And they want us to seriously consider their security solutions? Give me a friggin break!

​

 

Avast blames Microsoft for Win10 1803 upgrade blue screens, nonsensical options
Avast says it has fixed the problem that triggered Win10 April 2018 Update installation blue screens and dysfunctional 'boot to another operating system' options.
May 25, 2018
https://www.computerworld.com/artic...upgrade-blue-screens-nonsensical-options.html

 

I went to the MS support forum and noticed that Code: ab recommended fix was to disable "Fast Startup" in power options. Reviewing what I previously posted and factoring in the fix, I can see how all my posted issues could be related to power up issues at boot time. I never had the option enabled prior to 1803 and had none of these issues. Hopefully this will do the "trick" on 1803.

 

Fast startup was introduced in Windows 8. I know this option because for those dualbooting Gnu/Linux and Windows it is recommended to disable this, because of some problems with access to hibernated Windows NTFS filesystems from Gnu/Linux. Are you sure this option was not enabled prior to 1803?

Anyway it may fix that Windows issues. Probably they changed some details in the Windows implementation.

 

Hibernation was disabled on my PC prior to 1803. I manually enabled it; i.e. powercfg /hibernate on, when I upgraded to 1803 because I was having issues with my security software and though it might be related to hibernation. As such, Fast Startup option was N/A since it requires hibernation to be set on.

 

Windows Start Command Getting A /NewWindow Flag So Apps Don't Start in Tabs

https://www.bleepingcomputer.com/ne...-a-newwindow-flag-so-apps-dont-start-in-tabs/

 

Does anyone know, from the websites bellow, which are necessary for the Store to function?

Websites: https://pastebin.com/raw/5Da5pMMa

Thanks

 

Microsoft Added An Address Bar to Registry Editor in the April 2018 Update

https://www.bleepingcomputer.com/ne...-to-registry-editor-in-the-april-2018-update/

 

This was added quite some time ago. I don't remember if it was the anniversary build or the first Redstone...

 

Indeed, I've been using that feature since RS3 I believe.

 

The address bar, was first introduced, in Insider Preview Build 14942, which was released in October of 2016.

 

From the link:
"Update 5/29/18: This was actually released in the Creators Update, not the April 2018 Update. Can't believe it took me this long to notice! Thx to Giorarv for pointing it out."

 

Microsoft is forcing Windows 10 version 1803 on users who have deferred updates
May 29, 2018
https://www.theinquirer.net/inquire...rsion-1803-on-users-who-have-deferred-updates

Microsoft Investigating Reports of Forced Windows 10 April 2018 Update Installs
Computers configured to block upgrade getting the update
May 30, 2018
https://news.softpedia.com/news/mic...ws-10-april-2018-update-installs-521340.shtml

 

Thnx @anon for posting update of an article. I don't use Win10, so didn't know this feature was there before.

Edit: thnx to others for pointing it out also.

 

Hardening Microsoft Windows 10 version 1709 Workstations
May 2018
Australian Cyber Security Centre
Link: asd.gov.au/publications/protect/Hardening_Win10.pdf (pdf)

Really fantastic material here.

 

Yeah, but not much good for Home version of Windows.

 

Thanks for this!!

 

@Trooper You're welcome.