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.
It's funny to install windows updates if you have a somewhat slow (in modern terms) computer. Go get a torrented Windows 7 with updates rolled in till a few monthes ago. Install Windows.. with the custom stuff (updates + script that installs IE and .Net) it takes about two hours to install. .bat file found on the net to "unstuck" it, but dunno if the RAM ugprade did something or it wanted just one more reboot..)
Then it takes about an hour to boot, reboot, install Firefox (downloaded with ftp.exe), change wallpaper etc., install some shit and an AV (this is a single core low power PC with 1GB and old HDD)
Then it takes a shit lot of time to find Windows updates. Two days later, it's still not finding them!
I give up. PC's getting a pain to use, I go for upgrading it to 1.5GB or 2GB. cool, turns out I've plugged a 2GB module in, it now has 3GB. The PC still is miserable but has a lot of ram just like my everyday beast!
Wait.. Now the fucking "windows updates" software that was stuck at "checking for updates" now finds updates (about 63 of them). WTF? (I had tried some
So, in conclusion (tl;dr) there's some dark ugly voodoo that determines if Windows Updates will actually work. If it does, it's of course extremely CPU and memory intensive : if you have 1GB RAM or perhaps even 2GB RAM (which runs very low if you use programs) the PC could be so much fucking slow at installing updates that you run the risk of getting infected. I mean, two days of running Windows with unpatched old zero-days and what not! It makes me feels really dirty. Also, it's self evident that Windows 7 is about as bad as Vista on resources use.
But it was not like that time with XP + IE6 where I got obviously infected before I was even done setting it up.
Not sure if the Windows 7 PC is infected or not. Got to 98% memory use and swap hell with only windows (indexing etc. disabled), avast and firefox running (and task manager) ; firefox was only taking less than 20%. Had to kill firefox and disable the antivirus (killing firefox through task manager didn't go so well : not working, and "firefox is not responding" message not coming because of swap hell. Firefox got killed just when I had opened a command prompt which would have served me to kill it)
Got enough RAM to run, you guess it.. Windows Update! I installed that one critical update available and rebooted.
Who are you calling "plebs"? I'm offended!
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...)