Is windows 10 anniversary update causing you problems

Forums › Microsoft Windows › Is windows 10 anniversary update causing you problems

robjg63

2980 posts

Uber Geek

# 204826 19-Oct-2016 09:41

I was looking at getting a couple of HP laptops for work.

Noticed some hardware reviews where people had applied the Anniversary update and seemed to get a lot of issues:

Webcams not working (MS removed the ability to handle certain webcam stream codecs in W10 Anniversary)

Drivers for Audio crapping out.

Update getting stuck in a loop etc etc

Even a few iterations later - the update still seems to be a can of worms.

I ended up finding an HP page that had a list of devices they officially support on W10 Anniversary. There are many devices that are not supported.

Maybe this is really old news to everyone else - but are you having, or have you had issues?

Nothing is impossible for the man who doesn't have to do it himself - A. H. Weiler

1 | 2

3344 posts

Uber Geek

Trusted

Vocus

# 1653359 19-Oct-2016 10:29

4 people support this post

The whole update experience is crap.

My machine was unusable for over an hour while it "updated" when I switched it on (in order to use it!), with no way to prevent or stop it. Same with the kids.

Super frustrating and there is absolutely no need for it on a modern OS with copy-on-write capability. When you update a Linux, or actually any other OS (perhaps OSX aside) it just updates everything while the system continues to operate, you reboot, and you are on the latest everything, no fuss. Why have Microsoft gone so far backward in this regard? I don't remember ever waiting so long for updates to be applied, while the computer is rendered totally unusable.

Also not happy with feature and breaking changes being slipped in under the guise of critical updates, or the way all the MS crapware gets reactivated (onedrive, etc) every time.

huckster

375 posts

Ultimate Geek

# 1653364 19-Oct-2016 10:33

Father bought a new HP laptop (Envy x360) a few weeks ago. Worked nicely for a while then would fail to boot. We've done a factory reset and will be monitoring things carefully.

Problem is, he is half a world away which makes support interesting.

Do you have a link to this web page you mention?

bcourtney

652 posts

Ultimate Geek

Trusted

Subscriber

# 1653365 19-Oct-2016 10:35

Yep - Got a client with about 20 Probook 640 G2's running Win10 with the anniversary update and are having a number of issues with the audio drivers as well as random unresponsiveness.

The audio driver issue seems to be the most common among the laptops. Randomly after a clean boot Windows will report no sound devices installed. Re-installing the audio drivers resolves this but then again at some random point in the future the same issue occurs. Sometimes it is simply resolved by rebooting but other times it needs the drivers reinstalled.

Had one of them have touchpad driver issues too after an update and this was resolved by uninstalling the Samsung driver that Windows Updates forced on it and reinstalled the actual driver from HP.

Kiwifruta

1023 posts

Uber Geek

# 1653374 19-Oct-2016 10:45

One person supports this post

ubergeeknz:
The whole update experience is crap.

My machine was unusable for over an hour while it "updated" when I switched it on (in order to use it!), with no way to prevent or stop it. Same with the kids.

Super frustrating and there is absolutely no need for it on a modern OS with copy-on-write capability. When you update a Linux, or actually any other OS (perhaps OSX aside) it just updates everything while the system continues to operate, you reboot, and you are on the latest everything, no fuss. Why have Microsoft gone so far backward in this regard? I don't remember ever waiting so long for updates to be applied, while the computer is rendered totally unusable.

Also not happy with feature and breaking changes being slipped in under the guise of critical updates, or the way all the MS crapware gets reactivated (onedrive, etc) every time.

This is my major frustration with Windows 10 updates too. At the end of the work day, I choose 'update and shutdown', and the next morning when I boot up the computer, I spend an hour for the update process to finish. Very frustrating. Fortunately, touch wood, it hasn't happened when I needed to print something urgently for an appointment. I'm going to try 'update and restart' next time I get the option, so that hopefully the entire updating process is completed by the time I arrive in the morning.

I would use linux 100% but a couple of my suppliers are still in the dark ages and have windows only applications that I must use, the other suppliers use browser based solutions.

clinty

641 posts

Ultimate Geek

# 1653418 19-Oct-2016 11:13

One person supports this post

We have had a several clients with RDP issues after upgrading to AU (1607)
It seems to only affect 32 bit installations - symptoms is usually that RDP will load but not connect with an error about the remote server not being accessible

Temp fix seems to be to copy mstsc.exe and mstscax.dll from the windows.old directory ( the ver 1511 files) but these get overwriten the next time the client updates

Clint

Dairyxox

1493 posts

Uber Geek

# 1653433 19-Oct-2016 11:40

One person supports this post

Yes, I had a HP Elitebook here that got stuck at the lock screen after the update. It couldn't get to the login prompt.

Going into recovery and rolling back to the previous build got it the machine functional again, albeit without update. There are lots of reports of this issue (stuck at lock screen), with very few fixes if any.

I'm all for Microsoft making updates compulsory IF they can get it right.

At this stage, I wish they would acknowledge the experiment has failed and stop it. Its been a failure.

Coil

6615 posts

Uber Geek
Inactive user

# 1653435 19-Oct-2016 11:44

I had issues till no end.

My Win 10 pro licence was upgraded from 8.1 Pro to Window 10 Pro, The upgrade gave me windows 10 home, Support did something for me and it was activated again as windows 10 pro. That buggered up my office licence too. Called again.. Sorted.

Forcibly upgraded to 10 anniversary and back at square one, Non activated, office buggered. Support tried to tell me i was a pirate etc cause i threw all my discs away etc. Got there in the end but heck.

ubergeeknz

3344 posts

Uber Geek

Trusted

Vocus

# 1653516 19-Oct-2016 13:13

Dairyxox:

There are lots of reports of this issue (stuck at lock screen), with very few fixes if any.

Hmm actually I had something like this, happened twice so far since AU, after computer woke up from standby, just sat there at lock screen and disk churning endlessly (I left it for almost an hour), unable to log in. Had to use the old universal reset.

give it the fat finger

Oblivian

3358 posts

Uber Geek

# 1653518 19-Oct-2016 13:21

Pleanty of audio driver issues. Update and signing for 2 of the files (talking MS HD audio codes here) it uses goes west. Had to over-write them manually with 2013 dated versions before dev manager would accept they were signed and initialise.

Sideface

5411 posts

Uber Geek

Trusted

Lifetime subscriber

# 1653525 19-Oct-2016 13:36

I have updated 10 x Wintel desktop PCs to the Anniversary Edition with no problems BUT ...

it killed audio on my brand new Dell laptop.

I had to wait a month for a new audio driver - now works perfectly

Sideface

myopinion

862 posts

Ultimate Geek

# 1653530 19-Oct-2016 13:43

clinty:

We have had a several clients with RDP issues after upgrading to AU (1607)
It seems to only affect 32 bit installations - symptoms is usually that RDP will load but not connect with an error about the remote server not being accessible

Temp fix seems to be to copy mstsc.exe and mstscax.dll from the windows.old directory ( the ver 1511 files) but these get overwriten the next time the client updates

Clint

Another workaround is to connect to the remote location/server with a VPN first then RDP will work. PITA.

clinty

641 posts

Ultimate Geek

# 1654569 19-Oct-2016 17:01

myopinion:
clinty:

We have had a several clients with RDP issues after upgrading to AU (1607)
It seems to only affect 32 bit installations - symptoms is usually that RDP will load but not connect with an error about the remote server not being accessible

Temp fix seems to be to copy mstsc.exe and mstscax.dll from the windows.old directory ( the ver 1511 files) but these get overwriten the next time the client updates

Clint

Another workaround is to connect to the remote location/server with a VPN first then RDP will work. PITA.

Hmm ... interesting almost seems like it is by design then. Might have to dig into this further

Clint

networkn

21301 posts

Uber Geek

Trusted

Lifetime subscriber

# 1654579 19-Oct-2016 17:27

Worlds largest and longest beta test :)

Yes we have customers experiencing all sorts of issues.

Surprisingly my W10 machines have been more stable lately.

freitasm

BDFL - Memuneh
64673 posts

Uber Geek

Administrator

Trusted

Geekzone

Lifetime subscriber

# 1654588 19-Oct-2016 18:01

I have Anniversary Updated on two HP laptops (HP Folio and HP EliteBook). Both working fine, including Windows Hello with fingerprint reader on HP EliteBook.

Installed Anniversary Update on a Dell Inspiron 5000 and that worked fine too.

My technology disclosure | Digital Transformation | Enterprise Content Management | Customer Relationship Management | Data Insights, Business Intelligence and Advanced Analytics

robjg63

2980 posts

Uber Geek

# 1654589 19-Oct-2016 18:02

One person supports this post

Geeze it's as bad as I feared then - if not worse!
I suppose it will settle eventually..

ReHP officially supported hardware: http://support.hp.com/nz-en/document/c05195282
List looks big but I know how many variants HP have.

Nothing is impossible for the man who doesn't have to do it himself - A. H. Weiler

1 | 2