The Windows OS Thread - Formerly THE OS for gamers and normies, now sadly ruined by Pajeets

I am reminded of the .hack games where some guy managed to wipe out most of the devices connected to the Internet through a virus. The only computers to survive were running a random OS by a small company, which pretty much became mandatory. Just some food for thought.
off hand i would be very suspicious of that one company, as a universal virus would have such a level of complexity that it wouldn't be blocked by one singular OS from a small company
 
off hand i would be very suspicious of that one company, as a universal virus would have such a level of complexity that it wouldn't be blocked by one singular OS from a small company
The virus was written by a random teenager.
 
I don't understand how people are excusing Microsoft's culpability here - this was delivered via the internal Windows driver updater. The fact that Microsoft can not only hotload drivers to your running system but also doesn't even put them through some kind of validation process before doing so is a massive problem. It's been a problem for a while and this time it was a problem that went nuclear. Redmond needs to pull their heads out of their asses.
 
The outage has nothing to do with MS/Windows, it's all on Crowdstrike.

Fun fact, their CEO was CTO of McAfee about 14 years ago when McAfee caused a global outage.
Poor John Mcaffee - his name forever associated with that software. You know we never confirmed where we got those aerial photos of the temple on Epstein's island but Mcaffee was the popular theory. You'd need to be able to get relatively near the island in open waters, so somebody with a yacht, somebody with a decent aerial drone and above all - the sort of person who would actually do this. John Mcaffee fits all three and had the time and opportunity.

Later imprisoned over bullshit and died suddenly after announcing he thought people were trying to kill him.

Guy was awesome and his video on how to uninstall Mcaffee AV remains a classic.
 
I don't understand how people are excusing Microsoft's culpability here - this was delivered via the internal Windows driver updater. The fact that Microsoft can not only hotload drivers to your running system but also doesn't even put them through some kind of validation process before doing so is a massive problem. It's been a problem for a while and this time it was a problem that went nuclear. Redmond needs to pull their heads out of their asses.

Being able to update drivers without restarting is a good thing, not a bad thing. IBM z series has been doing this for decades, and you won't find a more stable, secure platform.

Crowdstrike broke Debian and Rocky earlier:

It's a CS problem, not an OS problem.

I was shocked to learn a few weeks ago that the order pickup lockers at Lowes, run Windows. I went to pickup something I ordered and it was boot looping and showing the Windows login screen. You could run those lockers with a Raspberry Pi, no problem, but nope, Windows. What a waste of money. I was wondering today if Lowes uses CrowdStrike and if they do, if they deployed it on those lockers.

The lockers are probably all being run from the same server. I doubt Lowes is paying for a full Windows license for each locker.
 
If it's on 20% of all business computers it can be considered as part of the OS.
The software is written by a 3rd party, and said 3rd party were the ones who pushed the bad patch. Microsoft had no involvement in the development or distribution of this issue. The only culpability they have here is with underlying design of windows (allowing these vendors to interact with the kernel directly in the first place). These are decisions from 25+ years ago and aren't something so easily changed. I'd argue many of the underlying issues with Windows are the result of decisions from 25 years ago, but its not something they can really change at this point. The real culprit here is Crowdstrike and their CI/CD Pipeline. This should've been caught by automated tests, and its asinine it was pushed to 100% of their customers instead of 1%. Businesses pay them because they're supposed to be reliable as a high end vendor, their bottom line really needs to suffer for this kind of fuckup.
 
If it's on 20% of all business computers it can be considered as part of the OS.
No, a third party application does not become part of an operating system once it reaches a certain install base. That's retarded, and you should feel bad for posting that.

The only culpability they have here is with underlying design of windows (allowing these vendors to interact with the kernel directly in the first place).

Crowdstrike bugs have caused kernel panic in Linux machines, too.

You can break any computer if you're diligent enough.
 
Why the fuck is it so difficult to get a secondary touchscreen monitor to work properly on Windows? I can plug in and use it, but it registers all touches as happening on the primary monitor, even if I try changing the "Tablet PC" settings. The only way I got it to work was running some weird commands in the terminal.
 
Why the fuck is it so difficult to get a secondary touchscreen monitor to work properly on Windows? I can plug in and use it, but it registers all touches as happening on the primary monitor, even if I try changing the "Tablet PC" settings. The only way I got it to work was running some weird commands in the terminal.
Everything related to touchscreen is in some way cursed. Everything.

In your case, what’s likely to be happening is something broke in your Display settings. I’d also check what the hardware settings are saying. (It’s likely not the hardware, but it’s like restarting; sometimes that fixes the problem because Windows is pretty resilient.) I also have no idea what OS you’re running, but then again, I worship at the altar of 7 on my tower because Windows 7 just works.
 
Everything related to touchscreen is in some way cursed. Everything.

In your case, what’s likely to be happening is something broke in your Display settings. I’d also check what the hardware settings are saying. (It’s likely not the hardware, but it’s like restarting; sometimes that fixes the problem because Windows is pretty resilient.) I also have no idea what OS you’re running, but then again, I worship at the altar of 7 on my tower because Windows 7 just works.
Win10. I don't know why it's mixing up the primary monitor and touchscreen, but ultimately I had to run this:
Code:
MultiDigiMon.exe -touch
tabcal.exe DisplayId=\\.\DISPLAY2

That let me set the correct screen and calibrate it.
 
I'm pleased with how willing modern Windows is to be cloned between drives and dropped into new hardware. A TPM clear, Microsoft account relog and firmware update later and everything works smoothly.
 
I'm pleased with how willing modern Windows is to be cloned between drives and dropped into new hardware. A TPM clear, Microsoft account relog and firmware update later and everything works smoothly.
Macrium Reflect images or old Windows .VHD style image backups? Just wondering.
 
Macrium Reflect images or old Windows .VHD style image backups? Just wondering.
Clonezilla in disk-to-disk mode, with proportional partition sizing (happily solves the recent issue of an inapplicable Windows security update due to small partition sizes, too!) I'm not actually manipulating system images-as-files or restoring from backups or anything exciting like that, just helping some folks migrate to new hardware despite their software configurations still being solid, and all that I need to do that is a Clonezilla bootable drive and external hard disk reader, because I'm a cheapass.

To assuage some fears, daily backups for users are performed on user directory files only, to a NAS and an offsite, but I don't have backups of entire user systems; I deem it an acceptable risk as setting up a new install isn't really that difficult, just a minor inconvenience that drive cloning circumvents when done in controlled circumstances.

This is the first time I've had to do it for a "complex" install with plenty of software I expected to complain, hence my surprise at the relative seamlessness of it. I suppose the advantage to the OS-as-a-service trajectory (and licence keys stored on the motherboard) is that MS isn't going to try and stop me from duplicating installs very hard anymore, so long as I (or rather, people in my position) keep paying for the cloud services.
 
Diablo 4 runs fine on my system, which has Windows 10 LTSC version 21H2. If you are still running version 1809 or older, I wouldn't be surprised there are problems running games since that build is over 5 years old at this point. If you have version 21H2, my first guess is your video driver probably need to be manually updated to a newer version. Windows LTSC doesn't like to auto update drivers as often as other versions of Windows.

I really like Windows 10 LTSC as a gaming platform but it does have some quirks, most of which have been covered in the Windows 10 LTSC for gaming thread.
This is exactly what I was looking for. Still on LTSC, tried to play The First Descendant last night and it is cranky about LTSC. I might have to upgrade to 11 to get these newer games to work.
 
Back