Windows 10: Solved - Win 10 Anniversary Update 1607 - The Worst Ever?

Yes, that is going to be a problem TP-Link has a driver for TP-Link TL-WN822N v4 so it sounds like you've got an obsolete device. I, too, dislike the direction Microsoft is taking with Win10, and I agree that it still has a lot of bugs, but you can hardly blame Microsoft when a hardware vendor no longer provides drivers for old devices.

Wireless adapters are pretty cheap now. You can get a new TL-WN822N on Amazon for $18.40 (US). It doesn't state it is v4, but it says it is supported on Win10. And there are a lot of others available if you want to be sure get get a supported one.

 

Well,, I guess for some they need a good vent/rant. But I sure hope that they stick around afterword's and get their issues addressed.

 

Beats throwing the device out the window. *Smile

 

No.. I love to imagine someone tossing the PC out the window or better yet.. into a wall. *Biggrin

 

The rant is a bit too long to read in detail, but this paragraph stuck out to me.

It is not up to Microsoft to provide device drivers; it's up to the hardware vendors. Microsoft provides some generic drivers but you are (almost) always better off getting drivers for the specific hardware you have. (If some of these devices are on-board, the manufacturer of your motherboard should have driver recommendations.) There were some cases when Win10 first came out that Windows thought it's generic drivers were more current than the appropriate vendor-provided drivers, but I think that has been cleared up.

I'm not a great fan of Microsoft, and I don't particularly like Win10 (in fact, I hate some of it), but blaming Microsoft for driver problems is waste of a rant time. Get and install the appropriate drivers from the hardware vendor. If the hardware vendor does not provide drivers for Win10, get new hardware. Then if you still need to rant, send it to Microsoft. (And, yes, I know I should follow my own advise.)

The people on this forum provide a wonderful service to us Windows users with problems, but they can't change the way Windows (or Microsoft) works. It's a waste of time to just kvetch here.

 

The issue comes down to this,, when there's an issue blame MS. I agree that it's not MS's job to deal with third party drivers. The makers have to keep them up to date and certified.

But, heck.. this type of complaint will be with us.. forever. *Shock

 

The first poster is the exception to the rule and not the rule. I personally installed the Anniversary Update on 7 of my own/relatives computers with absolutely no issues.
My cousin installed it on her 3 computers in New Jersey using my instructions with absolutely no issues.

Most of the people who have problems with Windows Updates have malware or viruses that have gone unnoticed on their computers or they are having physical hardware failures like my one cousin who I just had to replace her hard drive because it failed physically.

As to "Windows 10 doesn't like my driver anymore!" blame the driver maker. Period. They should be required to support their devices forever, even if it is just issuing a BAREBONES driver with no additional functionality to it.

 

Problems depend on the user's particular configuration. Generalizing from any installation experience - good or bad - is meaningless. And I don't think it's quite fair to write off problems as caused by malware or hardware failures.

I had 2 perfectly eventless upgrades to AU, but yesterday when I upgraded my wife's laptop I ran into what sounds like his point #3:3) Cold boot and resuming from hibernation now takes AGES! Prior to the 'much awaited' update a cold boot took around 50 seconds and resuming from hibernation tool hardly 15-20 seconds. Now cold boot takes around 2-3 minutes and resuming from hibernation takes around 1.5-2 minutes. It always gets stuck on the login screen and processes the entered password as if it is negotiating from servers situated on Pluto!Except my delays were more like 5-10 minutes. That is, 5-10 minutes before I powered off the laptop and tried again. But after the 5th or 6th reboot everything was fine. And who knows - it probably would have fixed itself after the first boot if I'd have let it sit for 30 minutes. Windows must have been doing some initial configuration setup, or installing drivers, or just being perverse. But now it's fine.

I seriously doubt that malware gave up and uninstalled itself. And I doubt that a hardware problem cleared up (but that's certainly possible). In any case, there were no suspicious events logged (that I noticed).

I don't think either my 2 easy installs or my heart-stopping 3rd install are representative of anything but themselves.

 

Yeah, Right! And they should stop making new products so they can supply free support for their old products forever. No company is ever going to provide product support forever.

 

I had this problem on an old Gigabyte motherboard from about 10 years ago. The problem was actually in the BIOS, not with the OS. The BIOS simply wouldn't complete POST with the USB dongle plugged in.

Have you verified that your BIOS is current?

 

But would you really want some device supplier to spend time creating a Win10 driver for a 5 1/4" floppy disk drive (for instance) instead of debugging its SSD driver (for instance)? And who takes over this "requirement" when a manufacturer goes out of business? And who is going to define and enforce the requirement? Yes, it's a pain when a device is no longer supported. But no company can afford to support obsolete devices forever. And, unfortunately for us, the manufacturer gets to decide when a device is obsolete.

 

I feel a device is obsolete when it is no longer in the supply chain, not available in stores, which then brings in no money to pay programmers to update the drivers after about the 3rd, 4th or 5th new Version of an Operating System and the drivers they have furnished for inclusion in the Operating System no longer work properly. Things started changing when WinXP Pro was available as either 32-bit or 64-bit but not much 64-bit software available and Vista as either with with more available hardware and software. It did take Microsoft a bit longer to get a 64-bit version of Office [Version 2010]. A case in point is the very fine DayTimer's DeskTopOrganizer that was dropped in 2010, apparently too many problems making it ready for coming systems. But now a large number of users have gone truly paperless with their Smart Phones.

 

Most people who have issues do NOT have malware or viruses. Both of my computers and my roommates are virus and malware and we have BOTH experienced the sleep/hibernate issue - on three different computers. Both of us have brand new SSDs that replaced older HDs. Putting the blame on the user is never a business tactic; yes, there will be people who have viruses and malware that causes issues, but not everyone does. Some of these issues are because M$ didn't bother to test anything before they released it.

And no where in my previous statement was I blaming M$ for driver issues. Yes, in the case of the OP and his TP-Link wi-fi, they should have made an driver for it; but in the case of the AU breaking people's webcams because M$ decided to not include a basic and popular video codec for a number of different manufactured web cams?

For now, all of my drivers work perfectly fine. The only 'out of date' driver I have is for the IMSE or whatever driver and the only reason I had to downgrade was because I was having sleep/hibernate issues. Which have returned a week after installing a new graphics card. And yes, the drivers are updated.

THANK YOU! This is my point - writing off issues that a number of people have as 'malware/virus', 'bad drivers', 'PEBCAK' belittles people who have genuine issues. I even stated that the AU on my laptop was perfectly fine; it's a Dell and it came with Windows 10. After I changed to a SSD, not only is it faster, but it works better than it had before.

When Windows 10 works, it's great! It loads faster on start up, I like getting the notifications, I would like the AU so I can get rid of Skype and just the app , I enjoy the live tiles. But most people don't come around to praise the OS - they're here because something doesn't work. And I have yet to see or read any Windows 10 update not breaking something. That's my problem. And on top of that, known problems that have been going on since beta still haven't been resolved - this sleep/hibernate issues for instance. I remember searching for this when I had the release and saw it was a problem in beta. Wasn't beta two years ago? Two years and we're still facing this issue? I mean c'mon!

Anyway, yes. I signed up for this site because the posters seem to be a lot more competent than the 'experts' on the M$ forum and will actually give real fixes to real issues. And that's what I have - an actual issue. Sleep/hibernate is not being caused by malware, I don't have any viruses, I'm not running anything illegal, like torrents or cracks; as of this morning, Windows is completely updated, all of my peripherals are updated, drivers are updated (with exception to that Intel thing); I have all of two USB devices connected - keyboard/mouse combo and game controller; I have a headset connected (for work); and speakers.

This issue was something that was fixed and has suddenly again and for whatever reason, I can't seem to get a simple answer on how to fix it. Fixing it, as the OP alluded to, shouldn't need me to go into regedit, I shouldn't have to reformat, I shouldn't have to only work in safe mode, and I shouldn't have to crack open my desktop. Yes, bugs will come about, but that's what testing is for. That way you minimize the amount of bugs and people who get hit by them. I like Windows 10, I do, I do, I do, but it's stuff like this that drives me crazy.

This is what ruins a perfectly good and possibly great OS - because M$ couldn't wait to get their money or redeem themselves with Windows 8.

 

Thanks for joining in mate. The thing is that since its official launch right from version 1507 --> 1511, the same TP-Link adapter used to work flawlessly with Win 7 x64 drivers. So it is not a problem from the vendors side. I compeltely agree that the vendor should be considerate enough to release latest drivers. But in this case MS is making the 'good' drivers, 'bad' for no real reason. I mean if they were working uptill 1511 then why cant they work on 1607?

Btw now my wifi adapter has started disconnecting itself more frequently, say every 15-20 mins. or so :<

 

You just upgraded to the 1607 AU update and there is only a 10-day period for when your windows.old will automatically be removed. There are too many variables going on to be successfully addressed within such a short time period. I’d like to believe it’s possible to revert back to the original Win10 pgrade. For those in the know, please advise.

With that said though you have major wireless connection problems. Why not connect wired?