I can see the rationale supporting that reasoning. It’s kind of like leaving leaving hyperthreading enabled on Intel CPUs: it’s a known risk factor but for a home user is unlikely to be an attack vector.
I took the latest Update recently, and now every time I try and Sleep my computer when I wake it up again I get a bluescreen, then the mobo can’t see the boot drive and I have to do a hard power cycle to get the system to boot again. Super fun.
stusser
4257
If it’s the cumulative update from last week, that’s the broken one, known for 40% CPU usage on searchUI.exe. Best bet is to uninstall it.
Diddums
4258
If you had the same Buffalo NAS I have (DualStation from almost a decade past) the clever folks on the Buffalo NAS forums have found a way to SSH into the NAS to enable SMBv2. It took about an hour all told, but now both a Win10 and Linux box see it just fine.
rei
4259
Do you have a link @Diddums to the NAS fix?
For the rest of ya, time to download and run Windows Update Blocker or run that command-line tool to prevent automatic download of build 1909 that may or may not hose your system.
Don’t say you weren’t warned.
Anyone know if this includes the Windows Subsystem for Linux v2?
Yes, yes, the sky is falling. Oh no!
rei
4263
Windows twice-yearly-updates (formerly called Service Packs) used to come once a year and were always the bane of my corporate rollouts. Since at least Windows 8 they have not been “delta change patches” but rather in-place reinstalls of the new build. That’s why you end up with that $WINDOWS.~BT folder afterwards.
Sometimes this goes off as planned, sometimes it doesn’t as evidence by my experience in corporate life and from previous posters in this thread. The last one was just in May with build 1903.
Microsoft promised this 1909 will be less of a big feature update but hey who knows?
stusser
4264
This one isn’t a full windows upgrade, actually, they changed that. Word is it’s a very minor upgrade and Microsoft is really moving to annual updates now. May 2020 should be a full one.
This is very good news as their QC is terrible.
rei
4265
They have no QC. They fired all the internal QC in 2014 and now rely on the volunteer Insiders program.
Well, that, but the other issue is that they’re using VMs for most of their internal testing, which is a terrible, terrible, terrible idea.
Diddums
4267
@rei Here you go.
https://forums.buffalotech.com/index.php?topic=24630.0
With SMB1 disabled on Win10, the old DualStation works after applying the above fix; but for some reason the share is only visible using Buffalo NASNavigator (from Win10). Ubuntu and Plex see it just fine. It’s not a problem, just a minor hassle.
Insiders or fanbois.
I think I’ll wait a few months and check El Reg before going for their “latest” feature/fiasco patch.
stusser
4269
I have a strong feeling this one is going to be fine. But yeah, waiting is always a good idea.
1903 just got an optional update (KB4522355) which may resolve some lingering resentment I’ve had toward the OS; supposedly doing away with black screens after updates, lagging at sign in, and resolving issues where the start menu wasn’t responding.
I got an update last night. So far, no problems.
So a stupid thing has happened recently. Notepad++ has become the default program to open .bat files with. So now I can’t run batch files.
How do I fix this? I assume if I just tell Windows to reset all default apps that may do the trick, but I’d prefer not to have to re-associate everything else in the process.
