Bork Tuesday, Any Problems Yet?

Awww Nutz !!

Foiled again :-(

Was able to delay a restart to finalize my second attempt at 1803 for a couple of weeks, but tonight the restart was baked-in and was unable to delay it any further. On reboot got 30% into "Preparing Your PC" and got a restart into "Restoring Your Previous Version of Windows."

The good thing is that my previous version was fully restored (last time the restore failed and had to reformat>restore WIN 8 from a Recovery USB to get an OS and then restored 1709 with Acronis.) But 1803 started to auto download as soon as I rebooted into my old 1709.

Read that article @mood posted this PM that explained how to delay download of 1803 with the Win Update Tool. Will have to try that to delay 1803 but may be too late since 1803 starts to auto download on reboot and/or start-up.

Dunno what's causing the update to 1803 to fail.

 

hawki,

Try updating to 1803 from an 1803 USB flash drive. Without internet connected. It always works for me.

 

First attempt = failed!

It is trying another go but after all the hassle I've had with that machine I doubt it will work.

I may just make that machine a Linux machine after all, especially if M$ starts forcing 1803 on it. So far it only receives 1803 when I've manually checked for updates.

 

Nope, 1803 failed again.

That's it, I'm not fighting Windows. As soon as 1803 is forced on that machine it will have a Linux distros installed.

 

Build 1803 is working fine for me, on a few computers that I've upgraded or done a clean install on. It refuses to install on my main computer, for now and at the moment, I couldn't be bothered deciphering upgrade logs, to find out why it fails. Creators Update runs really well, so I'm not in a rush.

 

Your compatriot likes this one.

 

Yeah, I seen that.

Ubuntu, Lubuntu, Kubuntu + possibly other 'buntus'. What to choose with them seeming to be so similar to a Windows users.

I just downloaded the latest Cinnamon Mate and burned an ISO (for now)...

 

Hi Stapp,

I've tried wiping the SSD from the latest 1803 ISO and clean installed - that resulted in repeated BSODs.. Is that similar to what you mean?

No, I haven't removed the drive and wiped it from another machine.

 

Your words, not mine.

 

@Brian K

Thanks for the suggestion

 

I wrote this info three years ago...

 

May Windows and Office patches are now relatively stable, but Win7 NIC problems persist

https://www.computerworld.com/artic...ely-stable-but-win7-nic-problems-persist.html

 

I've set my connection to metered, to block the download of April's update. I was bitten badly with Fall Creators update, which persisits in being buggy on my PC.

Is it wise to bite the bullet and upgrade now, or wait even longer for any bug fixes with patch Tuesday later this month? I have itchy fingers.

No Avast, no Intel ssd (my ssd is Crucial).

 

I must be lucky. I always upgrade on day one. No problems.

 

FWIW, based on my personal experience, I say go for it. I updated on April 30th, and haven't experienced any issue. When I got my W10, I started with version 1607, the upgrades to 1703 and 1709 I did them using the Update assistant and this time did it by clicking Check for updates, good result either way.

Thankfully, I don't use AV or any security programs that can block or interfere with Windows updates. Or, use programs that mess with Windows (I only disable what can be disabled in Settings or registry by yourself). In my opinion, this helps the process of updating Windows. If you are using third party antivirus or any other security program that blocks stuff from running, to help the updating process, I would disable this programs or better, uninstall them, and reinstall after the update gets done. I would even wait a couple of days before reinstalling them so Windows settles down without interference from this programs. Thats one thing I noticed with Windows 10 upgrades, they take a while, a few reboots and a few days before things really settle down.

Another thing I recommend you do is to disable fast start after first reboot after upgrading to Spring update. I didnt get to experience the black screen during reboot, the one that last for minutes but the second reboot after upgrading, the screen stayed black for a few seconds, I noticed it and wondered about it, thankfully nothing bad happened. So, after rebooting the second time, I disabled fast start and at no time ever since I have seen anything suspicious during reboot. Part of my routine is to disable fast start after upgrades as it gets reenabled, I never been in a hurry doing it but from now on, I will disable it before rebooting the second time after upgrading.

Why I ran the update on the 30th? I want to get that type of update out of the way. Do them and forget about them for the next 6 months. Otherwise, I ll be thinking, Am I gonna get it, when I am gonna get it, should I do it or not do it, too much pondering about it. And it can get worse, what about if you turn on your PC and there is the update in front of you as the machine decided to give you the update and you have to go out. To me, that can be messy because I want to baby sit this type of update. So, I do them at my own terms, and relax for the next 6 months.

Bo

 

FWIW, I just installed Windows Updates on two 7x64 machines. I created Macrium Reflect images first (being more cautious than usual) and made sure to go after the security-only rather than the cumulative download. When I do Windows Update installs, I usually reinstall Chrome browser at that time too (a little issue with Chrome desktop icons changing after WU). Today I also upgraded my VPN version. So there were a few things flying around, which isn't an ideal way to go about upgrades, but I have those fresh backups, and everything has turned out fine, so far. Like I say, FWIW.

 

What is a "hidden update?"

How does an update get "hidden?"

Talking in terms of wushowhide.

 

FWIW, I decided to update to April update. Uninstalled KIS and MBAM first, and the install went smoothly, sweet as a nut!
Now it just needs to be seen if fastboot is to be re-enabled. I disabled it as a 'cure' for random reboots on Fall creators update. A bug MS refuse/d to fix.

 

I just received several Office patches through Windows Update (we are still using Office 2010 at work) and now my Outlook keeps crashing as I try to type emails. Microsuck needs to get their act together.

-Update: Though it continued to crash all of the rest of that day, it has been fine since then. I had rebooted on that day, so I would not think that would be the issue.

 

After updated 1803 on a Dell 7368 the hello face login is hit or fiss. Worked fine on 1709

 

I've installed Windows 7 latest Cumulative update and all updates for Windows 10 and did not notice any problems so far.

 

Based on this I expected SMBv1 issues but updated 2 machines for test and everything seems fine. Nobody seems to have the details of what issues are, so at this point I am not going to worry about it unless I encounter a problem.