Cumulative Update KB4469342 Windows 10 v1809 Build 17763.168 - Dec. 5 Win Update

brummyfan said:

I have uninstalled this update as I prefer 17763.134 to have stable wifi connection.

Was your wifi connection dropping with this update?

g41851 said:

Was your wifi connection dropping with this update?

Yes, this update makes it very unstable.

brummyfan said:

Yes, this update makes it very unstable.

Sorry to hear that, hopefully the next update will be more stable for you.

g41851 said:

Sorry to hear that, hopefully the next update will be more stable for you.

It's OK, Thanks anyway, I am quite satisfied with the previous build.

brummyfan said:

Yes, this update makes it very unstable.

What wifi chip? My wifi has been perfectly stable on .168 - Intel Dual Band Wireless-AC 3168NGW

sgage said:

What wifi chip? My wifi has been perfectly stable on .168 - Intel Dual Band Wireless-AC 3168NGW

It's a Killer Wireless 1535.

brummyfan said:

It's a Killer Wireless 1535.

Hmmm... that uses an Intel Wireless-AC N1535 chip. Just trying to see if there's a particular chip or brand that has/had problems. I have not had a problem with wireless at all with my Intel wireless. Weird that these driver regressions keep coming back...

brummyfan said:

It's a Killer Wireless 1535.

I have a Realtek USB stick, was dropping out a lot until I installed new driver from Realtek's site. Now it's solid.

sgage said:

Hmmm... that uses an Intel Wireless-AC N1535 chip. Just trying to see if there's a particular chip or brand that has/had problems. I have not had a problem with wireless at all with my Intel wireless. Weird that these driver regressions keep coming back...

I haven't had WiFi problems for a long time with this laptop until this update, I have reverted to the previous build and the WiFi behaves normally, anyway, I have sent a feedback, let's see what the future update do.

flhthemi said:

I have a Realtek USB stick, was dropping out a lot until I installed new driver from Realtek's site. Now it's solid.

It's good to hear the driver update solved your problem, I am waiting for the next update because build 134 works fine at the moment.