Windows 10 Anniversary Update OK?

Topic

New Reply

Just got this from reader NP: I have been following your articles about issues with Windows 10.  Would you say at this point, it is safe to update, or
[See the full post at: Windows 10 Anniversary Update OK?]

Reply | Quote

Replies

1611?? or 1607 for Anniversary Update. I’m confused.

1 user thanked author for this post.

PKCano

Reply | Quote

Ooops! 1607 for sure.

2 users thanked author for this post.

woody, Bobc

Reply | Quote

Is this question about whether to upgrade from 1511 to 1607?

I had a perfectly stable environment in a well-tweaked build 1607 system running in a virtual machine. Honestly, I never had any problems with any of the updates.

Big picture-wise, I’d say that Microsoft’s promotion of the Windows 10 system to CBB (“Current Branch for Business”) status seems to be a good indication of when it’s quite safe to update from an earlier full version.

For what it’s worth I presently have a stable, functional Creator’s Update (version 1703) setup now too in a VM.

Suggestion: If you really, really want to know whether the next new version of Windows is for you, set up a virtual machine environment (e.g., with something like VMware), install the new OS, and test it for yourself. It’s how those of us serious about having a good, solid new OS to move to do it.

-Noel

1 user thanked author for this post.

Elly

Reply | Quote

It was a typo – 1611 instead of 1607

Reply | Quote

I got that. I was wondering about the basic question being asked by NP…

I think the basic question is whether to move up to version 1607 from its predecessor, 1511 – which is why I crafted my answer above the way I did.

At this point it’s hard to imagine that some folks have been putting off THAT upgrade, when even the NEXT version is out and is already reasonably stable. But I’m not really the one to talk, I’ve only run Windows 10 in a virtual machine; I’ve still not upgraded my hardware to Windows 10 at all. It’s just not “better enough” yet.

-Noel

Reply | Quote

well Noel C., Microsoft will soon end support for Win10 v1511 near the end of 2017 (like MS did for the v1507 RTM release this May 2017), so it IS time to move on to at least the 1607 release.

heck, I’ve just tested a Win10 upgrade from an RTM build (1507) to a 1703 release on an old Dell Inspiron laptop that used to have Vista. yes, you CAN do this; leapfrog from 1507 to 1703 though I always install feature updates from either a DVD or USB install media.

Reply | Quote

Like it or not, but W10 has been the most virus-resistant OS M$ has made in a long-time.

Fortran, C++, R, Python, Java, Matlab, HTML, CSS, etc.... coding is fun!
A weatherman that can code

Reply | Quote

Can’t windows 10 be infected by a non-SMB vector such as email attachment?

Reply | Quote

We let a couple of test machines take the Win 10 1703 Creators Update, and while the OS seems perfectly stable – some of our Engineering and Architecture specific applications do NOT like it at all.  (They seem good on Win 10 version 1607.)

I would say wait until it goes to CBB, and then test the heck out of it for your use case before widely deploying.

~ Group "Weekend" ~

Reply | Quote

While running the AU in virtual machines does not cause much issues, it’s different when installed on bare metal. The most annoying issue is that the AU won’t boot into the desktop after installing Windows updates. On the other hand, the CU is quite stable.

Reply | Quote

what kind of computer are you using, mr anonymous?

I’m not experiencing the problem on a friend’s custom built PC using an ASUS M5A78L-M LE/USB3 motherboard with Windows 10 AU v1607. the desktop loads perfectly after installing the latest windows updates for AU.

Reply | Quote

(some other person replying)
Perhaps anonymous has hardware that microsoft is pushing incompatible drivers for. Install updates (and drivers) = no boot. Solution, revert, stay offline until microsoft fixes it?

Reply | Quote

Happens on different Dell XPS and Samsung models. Whatever, CU works fine and AU is out of support in the near future anyway.
It’s caused by the Local-Session-Manager-hung-on-start issue.

Reply | Quote