Samsung Cripples Windows Update To Prevent Incompatible Drivers
jones_supa writes: A file called Disable_Windowsupdate.exe — probably malware, right? It's actually a "helper" utility from Samsung, for which their reasoning is: "When you enable Windows updates, it will install the Default Drivers for all the hardware no laptop which may or may not work. For example if there is USB 3.0 on laptop, the ports may not work with the installation of updates. So to prevent this, SW Update tool will prevent the Windows updates." Too bad that the solution means disabling all critical security updates as well. This isn't the first time an OEM has compromised the security of its users. From earlier this year, we remember the Superfish adware from Lenovo, and system security being compromised by the LG split screen software.
Does their warranty cover hacked laptop?
Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
I can think of two solutions on how to solve this problem.
1) Pin the installed OEM drivers, so that Windows understands that no other drivers should be installed for these device IDs.
or
2) In the PCI device ID, add extra information that this device is a special Samsung variant, and then Windows knows that the generic driver for that device is not compatible.
I'm not sure if these solutions are possible, if someone knows more then please let me know.
It would've been far simpler and less controversial for Samsung to just turn off the Windows 8/10 equivalent of Windows 7's "[right click on your computer's icon]->Device Installation settings->Do you want Windows to download driver software and realistic icons for your devices" option in the "Devices and Drivers" control panel and provide their own "driver update" program. I don't have a Samsung, for all I know, they may already have a "driver update" program. I know at least 2 major Windows-PC vendors do have their own "update" programs that include alerting users when their drivers are out of date, and it wouldn't surprise me if Samsung was doing the same.
Given what Samsung is doing, if Samsung provides its own "Samsung Update" that (by default) automatically takes all critical Microsoft Updates and which at least gives the user the option of taking vetted non-critical updates (or even better all Windows updates EXCEPT conflicting driver updates) AND keeps this running as long as Microsoft continues to allow access to its "Windows Update" functionality (which is presumably longer than the "10 years" it promises to keep fixing security holes) then I can see this being "not all that dangerous." However, if they do this they need to make it VERY clear to the buyer that Samsung, not Microsoft, is taking responsibility for keeping the operating system up to date.
Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
Unfortunately, not all driver updates fall under the optional updates. I agree that most are, but I had a client come to me saying his wireless driver was "missing". It was installed, but non-functional. Oddly, it didn't show a "failed to start" yellow triangle or any other anomalies in the device manager. I rolled back the driver and checked Windows Update to find an "Intel Centrino Wireless-N" critical update. It kept installing automatically until I hid the update. It is rare that this happens, but does from time-to-time.
I bought a Samsung laptop. i5, 6gb ram, Hybrid NVIDIA and Intel graphics, 750gb HDD, DVD burner. It is light, well powered and cost efficient back in 2011. Windows 7-64 bit. Problem is: Even the keyboard hotkeys such as screen brightness, WiFi, etc. work only through a "Control panel" that takes ages to load. Volume keys don't work within a game and sometimes the trackpad stops working after sleeping. And also I don't dare installing Linux on it because I read about severe cases of linux bricking the UEFI and rendering the laptop completerly useless.
Alas, after you start it up (either from off or sleeping) and wait the 10-15 minutes for the HDD to calm down (after stripping down the startup, defragmenting, ccleaner and the such) it runs really well.
Windows 2003 had a 64 bit version, but Windows 2003 mainly was 32 bit. If you used the /PAE option on the 32 bit edition, you could get past the 4GB barrier on that OS... but the caceat was only if you had the enterprise or data center editions (which got you to 32 GB or 64 GB respectively.)
So, I do agree with the parent... the ability to get past 4GB did exist, but required a bunch of flaming hoops to go through.
As for monitors, I've seen lots of screwy, nonsensical stuff, stuff (such as a glitch on a SCSI card causing the monitor to tint green), so I wouldn't be surprised if this was the case.
Well there's certainly a prominent example of a company taking explicit aim to *break* knock-off devices in a driver update:
http://arstechnica.com/informa...
XML is like violence. If it doesn't solve the problem, use more.