Windows 10: merge the bugs now, we'll fix them later

[xtabber]

Folk who flog software for a living should read this Ars Technica article about what’s wrong with how Microsoft develops and distributes Windows 10.

After a year using Windows 10, I much prefer it to Windows 7 generally, but find it remains too unreliable to replace Windows 7 on my primary working system. The problem is that with Windows 10, I can never be confident that something that worked one day will continue to do so the same way next day, even if I haven’t changed anything myself. 

One shouldn't use beta software in a production environment, but Windows 10 seems to be stuck in a permanent beta.

[wraith808]

Since I've turned off updates (finally finding a real solution) and manage them myself, it's been great.  There are several things I like better on Windows 10, but am now glad that they aren't diluted by the terrible update policy.

[Deozaan]

I can't think of anything that has been broken by Windows 10 updates on my machine. Sure, many of my customizations have been reverted to their defaults, requiring me to re-customize things. I'm not saying Windows 10 updates haven't been bad for people, because surely some people have had issues. But I've never had a bad update experience with Windows 10.

I actually had more trouble on my machine due to a faulty Windows 7 -> Windows 10 upgrade that broke various things throughout the OS. But once I did a clean install of Windows 10 (about a year ago) all my troubles went away.

[4wd]

I can't think of anything that has been broken by Windows 10 updates on my machine.

-Deozaan (October 21, 2018, 04:42 PM)

I can, SAMBA v1 has been disabled by default after Windows 10 updates. 

Now I have to access my 4TB NAS, (no updates available), via FTP because re-enabling it didn't work on my computer.

Only reason I found out why it no longer worked was because DOpus opened a window telling me why along with a link to Microsoft Knowledge Base ... File Explorer just failed silently, (or spun its wheels), after a few minutes twiddling its thumbs ... nice.

[Stoic Joker]

I can, SAMBA v1 has been disabled by default after Windows 10 updates.  Now I have to access my 4TB NAS, (no updates available), via FTP because re-enabling it didn't work on my computer.

-4wd (October 23, 2018, 06:42 PM)

You mean SMBv1.0/CIFS File Sharing Support? We've run into issues with that on a few network devices, but never had a problem with reenabling it on Win10. It is however in two pieces for Client and Server connections under Turn Windows Features On and Off.

IIRC a reboot is required.

[4wd]

Tried re-enabling it through Windows Features, had a few reboots since, still doesn't work.

Tried re-enabling through PowerShell also.

Tbh, don't miss it that much for that device since it connects faster through FTP and I can use multiple credentials concurrently, (always had to clear them under Windows to access another account share on the device).

[rgdot]

Haven't touched latest Win10 update but previously the only 'major' (I would call it major) issue I have had  - sample size of several pcs upgraded from 7 or clean installs - is Recent Items being broken. A while ago I posted about it a few places including here, finally after not finding a solution I turned it off on the problem pc.
Frankly Linux Mint updates have broken more things for me, coincidentally Samba more than once, unfixable after trying purge/uninstall/reinstall/edit conf file ...