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

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
So back in the day, you used to be able to just install Windows overtop of itself without breaking anything. A friend of mine managed to break his Windows installation by pulling the powercable out accidentally. Apparently you can't do this any more? The option I get is to "Reset my PC" which nukes apps, etc? What is the sane way to deal with a broken Windows in 2025 without breaking everything?
 
analrapist said:
So back in the day, you used to be able to just install Windows overtop of itself without breaking anything. A friend of mine managed to break his Windows installation by pulling the powercable out accidentally. Apparently you can't do this any more? The option I get is to "Reset my PC" which nukes apps, etc? What is the sane way to deal with a broken Windows in 2025 without breaking everything?
Click to expand...
Boot from an ISO, enter recovery mode and DISM/SFC the installation on the drive? It's how I fixed unbootable Windows XP installations a few times.
 
I'm back, fam, I'm baaack!

Apparently, the new NMVe driver doesn't change much. I did a quick read test on each drive before and after, and all differences were within margin of error.

Perhaps it will work its wonders elsewhere, like with lower CPU load.
 
Overly Serious said:
How in the fuck is it the tail end of 2025 and Microsoft are only just doing native support for NVME? How did I not know this was a thing? And it's not even available outside Windows Server 2025, I'm inferring from this.
Click to expand...
They ran it through a SCSI emulation layer. It made sense as it allowed widespread compatibility, if you really want to you can use this to get NVME working with NT4. It's just NVME speeds got much faster in the past few years and that layer has become a serious bottleneck especially in server workloads.
 
Slav Power said:
Windows 11 is literally the worst thing that was ever made and is literally unusable.
Click to expand...
that's true though, especially after a feature update :smug:
got a BAD_CONFIG on a relative's notebook that even trying to restore the OS via pen drive didn't work, had to visit a fren in order to read the M2 and backup the data before needing to reformat everything, the installation simply could not be repaired and it was a official one, even recovery mode was giving BSOD.
Overly Serious said:
How in the fuck is it the tail end of 2025 and Microsoft are only just doing native support for NVME? How did I not know this was a thing? And it's not even available outside Windows Server 2025, I'm inferring from this.
Click to expand...
word? if true then i might import some shitty X99 chink xeon E2350 then to slap windows server on it to keep as a file archive, already got the NVMe prepped and ready but i was gunning for W11 IoT, if they roll this update then i might just give the middle finger to win11 in this specific case.
 
Last edited:
I recently reinstalled Windows 11 using an Microwin ISO generated from WinUtil. The source ISO was a December 2025 24H2 I grabbed from files.rg-adguard.net (very useful site for sourcing both new and old Microsoft software BTW). Annoyingly Explorer was somewhat broken and was using the old ribbon interface instead of the tabbed interface. Tried a bunch of fixes, but nothing worked to restore the tab interface. Reinstalled generating another Microwin ISO, but using an old 24H2 ISO I grabbed from Archive.org. This time no issues. Just posting this is a warning that using new Windows ISOs with the Microwin function of WinUtil might not be a wise idea. Here's a recent bug report from someone using the latest 25H2 ISO describing a similar issue that I had: https://github.com/ChrisTitusTech/winutil/issues/3813
 
Curry Teafag said:
Just entered the magic command. Gonna see you after the reboot with a much faster NVMe.
Click to expand...

Curry Teafag said:
I'm back, fam, I'm baaack!

Apparently, the new NMVe driver doesn't change much. I did a quick read test on each drive before and after, and all differences were within margin of error.

Perhaps it will work its wonders elsewhere, like with lower CPU load.
Click to expand...

I haven't tried yet. Backing everything up first! :o

It is possible that you have your manufacturer's drivers already in place and therefore will see no difference. Need to check under the Storage Controllers in Device Manager and see if the driver is the standard stormvme.sys. I'm probably being patronising - apologies if so - but useful context for others at the least.

Will have to do some benchmarks of my own as well. If there's one area of hardware I'd like more than any other to be improved right now, it's storage speeds. I keep meaning to look into setting up some sort of automatic RAM disk and seeing what I can do with that to speed up various operations. Having done some front-end stuff with NPM recently, and all its bajillion unnecessary files, doing my dev work on a RAM disk might be nice to try.
 
Overly Serious said:
I haven't tried yet. Backing everything up first! :o
Click to expand...
Heh. In fact, it made my second SSD 'disappear' by removing the drive letter from its partition. But the data is all there. It only did that to the only partition on the non-system SSD, which acts as D:. It did not change drive letters for the partitions on the system SSD, which act as C: and E:, not counting the hidden EFI partition.

This may generally be a low-risk operation, but keep in mind that Windows (including Windows Server; talk about enjeetification) does have the above-mentioned quirk, and if you rely on a second SSD on startup, that startup might fail.

Overly Serious said:
It is possible that you have your manufacturer's drivers already in place and therefore will see no difference. Need to check under the Storage Controllers in Device Manager and see if the driver is the standard stormvme.sys. I'm probably being patronising - apologies if so - but useful context for others at the least.
Click to expand...
No need to apologize. :)
The switch went through correctly. I do see Storage disks in Device Manager, and the NVMe storage controllers are both using stornvme.sys.
Mind you I'm running this on a gaming laptop, not server hardware.

Slav Power said:
Pretty sure this registry tweak is meant only for Windows Server 2025, so if you run any other flavor of 11 it won't do shit.
Click to expand...
Yeah, this will only work on Server 2025 for now.
 
Slav Power said:
Pretty sure this registry tweak is meant only for Windows Server 2025, so if you run any other flavor of 11 it won't do shit.
Click to expand...
Right. I saw that but then when @Curry Teafag said they'd done it I figured maybe MS had already rolled it out in preview / insider or something. I mean, could have also meant that they had Windows Server, but does anybody actually run that?
 
Not many people are nostalgic for these, but I am. One of the childhood PC's I used ran it and I remember it very fondly.


Sounds as beautiful as the OS itself. Truly the pinnacle of Windows NT we never saw again. :semperfidelis:
 
Curry Teafag said:
They are on par with those from Windows 98, IMO.
View attachment 8306540
View attachment 8306541
Click to expand...
98 felt a little bit more grandeur while 2000 sounded more caring and welcoming.

Then you had the NT 4.0 sounds that were the pinnacle of might and power that NT Workstation represented back then.


It's a meticulous composition as well since both are the same sound but reversed.

To be fair though, you have a similar effect with the Windows 98 startup sound.
 
Curry Teafag said:
Yeah, this will only work on Server 2025 for now.
Click to expand...
Allegedly, it can be done on Win 11, too. You need to enter the following three commands (untested):

Code: 
reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 735209102 /t REG_DWORD /d 1 /f
reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 1853569164 /t REG_DWORD /d 1 /f
reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 156965516 /t REG_DWORD /d 1 /f
 
You must log in or register to reply here.
Back
Top Bottom