Microsoft issues new Windows 10 update warning

[ManofGod]

make 2 of us at the very least, all was golden one day, next day Windows reports as my BT and/or wifi is there, functioning correctly and/or cannot assign it an IP/Proxy invalid
(nothing I can do/did fixes/fixed since w/e this took place, therefore I surmise as beyond a fool neat things, Win 7 vastly superior in every way that

I USE MY COMPUTER

though not willing to go through the BS of forcing 7 to my x570 ryzen 3200 etc as the actual install to use was pretty painless
if not still BS have to set to metered, have to hunt for this that and everything else, set tiles etc vs standard desktop apps/tiles being THERE
and START MENU not the dual/triple wide eye sore segregation they did for the "start is back" crap show this so far has been (found my 1/2 arse way of mimic my 7 install)

anywho....I want/need my wifi/BT back, thank you MSFT twits...stop mucking with "simple"

allow the users parts to work, keep their internet and computing SAFE from intrusion/backdoor spying
be very vigilant in NOT potential open of holes (such as sharing by default vs private i.e only DL when I click go

^.^

maybe b4 end of year all us Ryzen folks ( the rest of course LOL)
get functional OS again, so can enjoy Holiday gaming action when is cold out there.

What mainboard with built in bluetooth do you have ?

 

[Monkey34]

Seems the issues don't end:

"Cumulative update (KB4515384) causes the NIC to fail to enable with a code 10 error. Microsoft has confirmed a new bug in Windows 10 1903 which can knock-out WiFI on Intel and Broadcom wireless cards; but claims it is limited to NEC devices."

 

[AceGoober]

So far I haven't experienced any of the reported issues - knock-on wood - with the latest patches installed. Search works correctly, no visible CPU resource surges, no issues to report.

 

[ManofGod]

Seems the issues don't end:

"Cumulative update (KB4515384) causes the NIC to fail to enable with a code 10 error. Microsoft has confirmed a new bug in Windows 10 1903 which can knock-out WiFI on Intel and Broadcom wireless cards; but claims it is limited to NEC devices."

Well, I have straight Intel Wireless cards in my Asrock boards and they are unaffected, just a heads up.

 

[lostin3d]

Admittedly the issue that happened to me might be unique. POST failed to completely finish. I should give a few more details though. Initial POST, o.k., then show's RAIDs/drive controllers, o.k., load Windows, seems o.k., then black screen with a hex code similar to changing ones I see during initial post except the system stopped there. I didn't write the code down and everything seems fine now. Highly suspicious since it only happened both after the update and when Windows took over from the BIOS.

Doesn't help that every day now reading more stories on different sites about things borked. Wifi broken for some, multi channel broken for others, and the plethora of other things mentioned in this thread. MS doesn't need to worry about competition. They're fully capable of taking themselves down.

 

[Lumpus]

Last week's update almost bricked my sister's pc - went straight on boot to BSD, until I did system restore to an older version and then completed disabled Windows Update.
Mine updated fine this time... but didn't the previous big update.

 

[lostin3d]

Last week's update almost bricked my sister's pc - went straight on boot to BSD, until I did system restore to an older version and then completed disabled Windows Update.
Mine updated fine this time... but didn't the previous big update.

To some extent I think that's what the WIndows Repair did to mine to fix it. Be fine since as well.

Just saw this over at Tom's: "Windows 10 Update's Latest Casualties: Action Center, Network Adapters (Update)"

 

[ManofGod]

To some extent I think that's what the WIndows Repair did to mine to fix it. Be fine since as well.

Just saw this over at Tom's: "Windows 10 Update's Latest Casualties: Action Center, Network Adapters (Update)"

View attachment 188109

Eh, I have moved onto the insider builds on 3 out of my 4 machines since yesterday and am good. Seriously, I must be the only one who does not have issues, at least the way these things are made to sound.

 

[Armenius]

I'm surprised anyone with half a brain installs patches and updates right away. Delay any updates/patches for a few weeks so that the rest of the public can beta test them and freak out first..... then no problems. This is nothing new or unusual and is standard practice for big business going back to the 90's.

Indeed. I just upgraded my home PC to 19H1, 5 months after it released. And 19H2 is just around the corner.

 

[andrewaggb]

I completely agree with delaying updates. I used to install them as they were available and broke my work pc twice. I have multiple vpn adapters (both windows and openvpn), dual nic's + wireless, and hyper-v networking. One of the big 6 month upgrades broke all my networking and I couldn't get it working again without a re-install. I had another windows upgrade that somehow messed up my office 365 skype desktop sharing that I ended up re-installing an older version of windows 10 to fix as well. That one really made me mad as it's office 365 and windows, it should just work. Apparently it was a somewhat common issue with the upgrade and they resolved it eventually but that was unacceptable as I required that for work. I think I waited 5 or 6 months to upgrade that release when it worked. Since then I've been pausing updates and delaying upgrading the major versions for months and things have been fine.

I also had a laptop that simply couldn't install updates, it would try and fail, for 6 months or so this went on until it finally started working. The only software installed on the laptop was chrome. It was a fresh windows 10 install and was only used for netflix.

But I also have 8 other windows 10 computers in my house that have never had any issues upgrading.

 

[Xero717]

The recent update has been causing BSODs for me related to winsock adpater, which i'm guessing is tied into this networking mess. I'm not sure what they're doing over there in Redmond, but I think its time to slow the fuck down and make sure things are right before throwing them out into the wild.

 

[Lumpus]

I spoke hastily about being fine with this update.... I'm getting occasional BSD's if I watch a YouTube video all of a sudden now. :?
Everything else (non-YouTube) seems ok

 

[primetime]

I spoke hastily about being fine with this update.... I'm getting occasional BSD's if I watch a YouTube video all of a sudden now. :?
Everything else (non-YouTube) seems ok

funny thing is same thing happened to me...BUT havent had a bsod since relaxing my memory timings/speed. I would get them same time watching videos with browser. Is your computer is stable?

 

[pendragon1]

Eh, I have moved onto the insider builds on 3 out of my 4 machines since yesterday and am good. Seriously, I must be the only one who does not have issues, at least the way these things are made to sound.

been on the fast ring since the beginning, ive had two minor issues that got fix by the next update.

Last week's update almost bricked my sister's pc - went straight on boot to BSD, until I did system restore to an older version and then completed disabled Windows Update.
Mine updated fine this time... but didn't the previous big update.

a windows update wont "brick" your device. it might hose the windows but its not "bricked"

 

[odditory]

a windows update wont "brick" your device. it might hose the windows but its not "bricked"

Very resassuring to a non-technical user whose computer is rendered unusable, when their PC boots into a BSOD after an update.

"Sure you can't use your computer and you'll have to bring it to a professional and pay money to get it un-fucked and everything reinstalled, but a guy on the internet says your computer isn't TECHNICALLY bricked."

 

[pendragon1]

Very resassuring to a non-technical user whose computer is rendered unusable, when their PC boots into a BSOD after an update.

"Sure you can't use your computer and you'll have to bring it to a professional and pay money to get it un-fucked and everything reinstalled, but a guy on the internet says your computer isn't TECHNICALLY bricked."

just use the proper term is all that's needed.

 

[Algrim]

just use the proper term is all that's needed.

Fucked. Happy?

 

[nilepez]

Very resassuring to a non-technical user whose computer is rendered unusable, when their PC boots into a BSOD after an update.

"Sure you can't use your computer and you'll have to bring it to a professional and pay money to get it un-fucked and everything reinstalled, but a guy on the internet says your computer isn't TECHNICALLY bricked."

Sure, but this isn't a non-technical user site.

 

[DeathFromBelow]

just use the proper term is all that's needed.

Who gives a flying fuck? If you're out traveling and a Windows 10 update breaks your laptop... your machine is now 'bricked.' Doesn't matter how technically proficient you are, you now have to spend money to replace it or fix it. Most people aren't walking around with a second machine and recovery media in their back pocket.

I've run Linux for years and never had an update break anything. There is no excuse whatsoever for Windows to be this broken.

 

[pendragon1]

lol I buy a new machine ever time I run into a windows problem.

brick
/brik/
verb
past tense: bricked;

1. 2.
   informal
   cause (a smartphone or other electronic device) to become completely unable to function, typically on a permanent basis.
   "installing an unofficial OS voids the warranty and may brick the phone"

fucked borked screwed all those would apply bricked doesn't.

 

[DeathFromBelow]

lol I buy a new machine ever time I run into a windows problem.

brick
/brik/
verb
past tense: bricked;

1. 2.
   informal
   cause (a smartphone or other electronic device) to become completely unable to function, typically on a permanent basis.
   "installing an unofficial OS voids the warranty and may brick the phone"

'Typically' is a keyword there, bro.

You can 'brick' your motherboard with a bad BIOS update. That doesn't mean it's actually permanently disabled, it just means its a real pain to get it fixed. If a Windows 10 update locks you out of your machine 'bricked' is a perfectly appropriate term.

I'm so fed up with the Windows 10 fan club. Telling people what words they're allowed to use is about as pretentious as you can get.

 

[pendragon1]

typically as in usually bro

 

[DrLobotomy]

Bricked means broke.

Sorry, Charlie.

 

[pendragon1]

who's Charlie?
bricked means broke and permanently dead, done, throw it out. that's what it meant since it was first used.

 

[DrLobotomy]

who's Charlie?
bricked means broke and permanently dead, done, throw it out. that's what it meant since it was first used.

 

[DrLobotomy]

'Typically' is a keyword there, bro.

You can 'brick' your motherboard with a bad BIOS update. That doesn't mean it's actually permanently disabled, it just means its a real pain to get it fixed. If a Windows 10 update locks you out of your machine 'bricked' is a perfectly appropriate term.

I'm so fed up with the Windows 10 fan club. Telling people what words they're allowed to use is about as pretentious as you can get.

I don't like windows 10. You are still wrong.

Bricked is broke. fubar. fucked up beyond all repair.

Just give it up. You're just wrong. It's OK. I'm wrong all the time. Just not now.

 

[DeathFromBelow]

Bricked is broke. fubar. fucked up beyond all repair.

Sounds like a pretty good description of Windows 10 in general. Can't even run updates without risking data loss.

 

[odditory]

Sounds like a pretty good description of Windows 10 in general. Can't even run updates without risking data loss.

At best it's Russian roulette to install any windows 10 update that's less than a year old.

I'm pushing it running 1809 since it only came out 10 months ago, but I needed WMR. Everything else I've got locked down - no store, no telemetry, no cortandro, no updates, no bloatware.

 

[Catscratch]

I have a 790fx + 1090t rig and windows 10 1709 that i can't really risk upgrading to newer builds right now. I have a silly bug. You know when you mouse over on taskbar and there are little window previews, they dont go away, like ever. I have to click their X

 

[ManofGod]

I have a 790fx + 1090t rig and windows 10 1709 that i can't really risk upgrading to newer builds right now. I have a silly bug. You know when you mouse over on taskbar and there are little window previews, they dont go away, like ever. I have to click their X

Sounds like a video driver bug, a really nasty one. What card do you have in that please?

 

[ManofGod]

Sounds like a pretty good description of Windows 10 in general. Can't even run updates without risking data loss.

I love Windows 10 since it is extremely robust, fast and stable. I cannot tell you the last time I got a BSOD that was not caused by something I personally did, like overclocking to far. That said, there are issues that do need to be fixed and that is a fact.

 

[ManofGod]

At best it's Russian roulette to install any windows 10 update that's less than a year old.

I'm pushing it running 1809 since it only came out 10 months ago, but I needed WMR. Everything else I've got locked down - no store, no telemetry, no cortandro, no updates, no bloatware.

Dude, if you are pushing out a build for a corporate network, those things you mentioned are commonsense stuff and is not a super duper thing at all, unless you do not know what you are doing. Although, pushing out just a year old build, and one with known issues, seems risky at best.

 

[Catscratch]

Sounds like a video driver bug, a really nasty one. What card do you have in that please?

GT 1030. There's another rig with fx 4300 cpu and gt 1030 but windows 10 is up to date. It doesn't have this issue. I read it could be about windows/file explorer.