Samsung To Stop Blocking Automatic Windows Updates
A few days ago, we mentioned that a piece of (nominally) utility software from Samsung was blocking critical security updates. Understandably, this isn't what users typically want. The Register reports that Samsung has now back-pedaled, though, and will be issuing a patch in the next few days to fix the glitch. (Users were able to manually install the updates anyhow, but the expected, automatic updates were blocked.)
However, as the Register notes: The thought of a computer manufacturer disabling Windows Update will have had the Microsoft security team on edge. But there's also Windows 10 to consider.
When the new operating system comes out, Windows Update will feed in fixes continuously, and if you're not a business customer those updates are going to be coming over the wires constantly. Enterprise users get Windows Update for Business, which allows them to choose when to patch, presumably after the plebs have beta-tested them.
Besides ordinary business concerns about stability and continuity, if you are running in a regulated environment (e.g. biotech) you are prohibited by law from installing those patches until your validation group has tested them.
sPh
When the new operating system comes out, Windows Update will feed in fixes continuously, and if you're not a business customer those updates are going to be coming over the wires constantly. Enterprise users get Windows Update for Business, which allows them to choose when to patch, presumably after the plebs have beta-tested them.
I saw the entry "Windows 10 and later upgrades and service drivers" show up under the products & classifications options on our WSUS server a good 3-4 months ago.
Interesting wording I thought, since all other entries under the "Windows OS" group are named specific to a major windows version, and as far as I remember have never said "and later".
It looks like Microsoft is really serious about copying Apple versions now, with the "10" not really being part of the version string but just being there, and using the minor version section as the new major version number.
Yeay for needless confusion!
But at least it still isn't as bad as Nintendo product naming I guess.
Who are you calling "plebs"? I'm offended!
...dunno if the RAM ugprade did something or it wanted just one more reboot...
RAM. I went through this recently building Windows 7 VMs from an orginal/early ISO. With 2GB RAM, it stalled and would never finish the updates. With 3GB it got further, but still stalled and showed no further progress after being left running overnight. With 4GB, no problem, you can actually update the OS!
My desktop system is in an update error loop (0xC1900101-0x20017) that apparently has no solution. Win 10 tries to update, reboots, fails without warning, reboots. I have to run a fortunately free boot disk which removes the attempted update, but certainly doesn't solve the basic problem. "Disconnect all external devices" .. yeah, fine, no improvement. So I'm stuck at Build 10074, and wish I could figure how to stop all updates entirely! (Oh, and trying to reinstall Win10 Pro Insider Preview from an .iso image doesn't work either.) Talk about being screwed .. and it worked so well too, until that update. Time to wipe and reinstall, I guess. Or just drop back to my Win 7 (fortunately saved on a separate hard drive) and wait for the official Win10 release.
I don't run Windows, but my daughter does. THANKFULLY, she is the only family member that insists she run it. She already hates her laptop because its slow. Just a couple of weeks ago, the keyboard and mouse just stopped working. I managed to boot Linux on it, so it seemed the hardware was still good. Some research pointed to forums lit up with other Samsung laptop owners complaining about this. Some found the solution - a recent windows update caused the Samsung driver for the keyboard/mouse to be replaced, rending it unusable.
Seriously, as the technical support for this entire family, this is the last thing I need.
... Samsung has now back-pedaled, though, and will be issuing a patch in the next few days to fix the glitch.
It was a *feature* not a "glitch" and that was/is the problem.
It must have been something you assimilated. . . .
Well, let me put it this way: What kind of crap is Samsung shovelling out that the basic keyboard/mouse drivers which run on basically _anything else_ are able to render Samsung's hardware inoperable?
Plus: What kind of inept stunts is Samsung pulling that their drivers are automatically replaced?
Then again, given their track record with the developer's nightmare that is Tizen, this shouldn't surprise anyone. I mean, what is one supposed to think of a company who thought that an error message like "NAUGHTY PROGRAMMER!!! SPANK SPANK SPANK!!!" is a good idea? (Seriously: https://developer.tizen.org/de...)
I cared enough to waste that much time writing that too long post above. That shall be a reminder to how much time is wasted installing windows. Yup with another OS and an equally slow PC you can be done in about 20 minutes.
You tried to install Windows 7 on an old machine with only 1GB RAM?!!
Microsoft's minimum system requirements say it will run on 1GB RAM for 32-bit or 2GB for 64-bit systems, but you already found how well that works. The practical minimum for Windows 7 is 4GB. Anything less is like trying to drive a dump truck using a chainsaw engine.
--