New
#160
I spent all day yesterday working on my laptop after the update was causing a continuous boot loop. I delayed the install until next week, but my update controls are gone, so I couldn't delay any further.
Then the update failed on my desktop. Didn't stop working, the update just gave an error message, so after reading this thread I delayed updates for 4 weeks. Then I wake up today and it's bricked, no signal from the video card. Mind you, this is a machine where I just reinstalled Win 10, due to ongoing problems with updating to 1709.
Microsoft: If you're reading this thread, it's clearly a problem (like the last major updates) when a massive number of users have to reinstall your OS every time you release a major update, that's not ideal. You're doing a hell of a job turning people on to Linux and better hope Wall Street doesn't figure out what's going on.
You couldn't, even if you wanted to. For Edge and IE updates for Flash can only be installed through windows update.
Try going to https://get.adobe.com/flashplayer/ in Edge or IE and you'll be redirected to a page saying "Flash Player is integrated in Windows 10. You do not need to install Flash Player."
Having the same issue in one laptop I had with other after installing 17134.5: after restarting, the system gets stuck in a black screen with spinning circle. Thankfully, booting into Safe Mode and disabling/uninstalling Intel HD Graphics drivers fixes this, but the update installation is reverted. I seriously would like to know who's to blame, Intel or Microsoft developers? Or both?
That is not what I meant. Links to ms update have been posted to do the update manually via .msu files.
What I was saying is the cumulative update must have included the flash player update. I went to the adobe flash help site with edge. They have a check button there that will show you the version and tell you if the browser is up to date (you must have flash enabled for the site). Mine was up to date.
You're welcome, I'm not familiar with O & O Shutup...
@ddelo
Just realised that the registry key (to get rid of the Insider message) is not there as standard (it gets created by GPO) and has to be manually created first w/o it - thus the proper PS command would be:
Code:New-Item -Path "HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" -Force | New-ItemProperty -Name "ManagePreviewBuilds" -Value 1 -Force | Out-Null