News for hackers. Stuff that matters.
Re:SolarWinds hackers were able to access Microsoft source code by michaelmrose on Thursday December 31, 2020 @08:14PM (#25599617)
People complain about forced updates because updates have come down that inexplicably break things. For example there was one update in 2020 that caused appeared to delete any files placed in the users Desktop folder (although the files weren't really deleted) and another which caused running chkdsk to corrupt users filesystem in a fashion that typically required fixing the filesystem offline.

Furthermore such updates which usually require a reboot can easily interrupt important work or a long running task.

Just yesterday my Windows install which exists solely to run steam and steam games updated and then committed suicide in a fashion that can't be automatically repaired and requires a reinstall with zero explanation. For reference the hardware is fine as is the Linux install on another drive. The windows drive is a ssd less than 6 months old. I can even mount the ntfs filesystem which appears to be just fine.

There is absolutely no excuse for not letting users pick when or if they would like to update their OS especially when their QA has completely gone to shit and they cannot realistically promise that their update wont break your install.

Re:SolarWinds hackers were able to access Microsoft source code by blibble on Thursday December 31, 2020 @10:05PM (#25600432)
ltsc is the solution, and even though all the MS sychophants will tell you it's for ATMs/medical equipment only: I've been running it on my 2019 gaming box for a year, and had no issues at all

... I hear keys on ebay are about $2

Re:SolarWinds hackers were able to access Microsoft source code by webmobdev on Sunday January 03, 2021 @06:32PM (#25626331)
What's Itsc?
Re:SolarWinds hackers were able to access Microsoft source code by AnHonestComment on Thursday December 31, 2020 @08:19PM (#25599672)
To concur:

My laptop running Windows hangs periodically requiring a hard reset... if I watch Hulu on Chrome. At least twice a week and sometimes multiple times a day.

At least Windows in the 90s had the decency to put up a blue screen — now it just hard crashes without any display or debugging information.

Telemetry and forced updates are a slap in the face on top of the quality regressions.

Re:SolarWinds hackers were able to access Microsoft source code by posperson on Thursday December 31, 2020 @09:14PM (#25600135)
Microsoft fired their Quality Assurance staff, hence the regressions in reliability: https://www.ghacks.net/2019/09/23/former-microsoft-employee-...
Re:SolarWinds hackers were able to access Microsoft source code by AnHonestComment on Thursday December 31, 2020 @09:21PM (#25600174)
I somehow missed that — thanks for sharing!
Re:SolarWinds hackers were able to access Microsoft source code by stinos on Friday January 01, 2021 @04:49AM (#25602068)
At least Windows in the 90s had the decency to put up a blue screen

This sounds like back then there were only crashes with a blue screen (and dump), and currently there's only hard crashes without blue screen. Both of them are not true. I.e. there are apparently types crashes for which it hasn't been possible in the past decades to come up with a bluescreen, othiing new there. It is just as likely, maybe even moe so, the difference in your particular case is your hardware/driver. It's of course possible there were effectively changes at the OS level in how hard faults are dealt with, but I wouldn't just assume so.

Re:SolarWinds hackers were able to access Microsoft source code by chinhodado on Thursday December 31, 2020 @10:37PM (#25600615)
That sounds like a hardware or driver thing, specifically related to GPU, rather than a Windows issue. You can try to disable hardware acceleration in Chrome.
Re:SolarWinds hackers were able to access Microsoft source code by AnHonestComment on Thursday December 31, 2020 @11:52PM (#25600957)
Sure, could be.

My testing pointed towards a DRM problem, since it doesn’t happen with other video streaming or with rendering outside the particular Chrome + Hulu combination.

My point is two-fold:

1. Even if the driver crashes, the OS should blue screen (like it used to) rather than just hard freeze the machine.

2. Using an HP laptop with Windows and Chrome to view Hulu is so mainstream it should “just work” — so it’s a sign of industry breakdown it doesn’t.