Threadripper and Windows 7

Any proof.. or ...

 

I've installed Windows 7 on the MSI Carbon X399, Samsung NVMe 960 M.2 (PCIe), and everything works exactly as it's supposed to. Have had this setup for months now (since late August), along with Windows 10 and macOS Sierra (more recently). All solid, including prime95 torture.

Only minor issues are during an install, USB 3 drivers, which you can do the install with a PS2 keyboard and use the keyboard to load USB 3 drivers from the CD later on, or you can inject them into the installer.

The only BIG problem is, knowing which windows updates NOT to do, which end up causing the "processor not supported" pop-up. I forgot which KB it is, but I did a fresh install now and installing one KB at a time and will post the cancer-KB so you don't install it.

Google search shows KB4015549 and/or KB4012218 which are causing the unsupported hardware pop-up, but I'm not sure.

Even got macOS Sierra and High Sierra installed, working flawlessly (way too much involved though).

Windows 7 and Windows 10 run rock solid for months.

 

So on most of my previous installs, I did all the KBs, and never kept track of which one caused the unsupported hardware error. And when uninstalling them, the unsupported hardware error remained.

So I did NOT do these two updates below, which could be the culprits, but it's too early to tell without a few reboots.

I did NOT do KB4041083 or KB4054518. The 3rd one, KB971033, is the windows activation one, so it doesn't matter.

As far as blue screen, I've seen nothing. Had a few lock-ups when clocked too high, but that's about it.

Hope this helps anyone who needs it.

EDIT: I am basically staying away from these 4 updates:

1. KB4041083
2. KB4054518
3. KB4032113
4. KB2952664

 

Glad to have tested these. The ones that google search shows didn't match these KBs.

So far after a half dozen reboots, that "unsupported hardware" does NOT appear. At this point, I will no longer do any updates since I know one of those two is the problem.

I am staying away from these 4 updates:

1. KB4041083
2. KB4054518
3. KB4032113
4. KB2952664

 

Threadripper here with gigabyte Aorus running windows 7.

Win7 uefi, two Microsoft NVME hotfixes and USB 3.0 drivers slipped into the install iso.
Turn off any and all references to legacy boot in the bios, turn off USB legacy compatibility then 7 should install with no issues.

If you have issues slipping the USB drivers then try to find or buy a USB 2.0 pcie card to use temporarily for kb/mouse as it will run independently of the bios and not interfere with anything

Originally I had issues slipping the NVME hotfixes and installing 7 on my previous fx series setup and ended up installing 7 onto a regular sata ssd then manually applying the NVME hotfixes, installing the NVME drive and then cloned everything over.

Thought I would have to do the same with x399 but the hotfixes worked this time around.
As for windows updates I installed all of them and then I ran a bat file that removes the bad updates, I'm not at my pc currently so I don't remember the site I got the bat file from but I'll help in any way I can if someone is having trouble, I see a lot of people having issues with the gigabyte board and win7.

 

Sorry mate, nothing personal, but I it BS. Show some proof and more details about your system. I spent like 2mo trying to install Win7 on Aorus and got nowhere, all posible combination in BIOS (even fully set for Win10) in legacy or UEFI mode on SATA or Intel NVme.

 

Any proof or what...? Are you the Spanish Inquisition
The instability I experienced was due to incompatible RAM. Corsair Dominator Platinum v. 5.20 doesn't work on Asrock Taichi X399!
Windows 7-64 installs and boots on Samsung NVMe 960EVO and runs perfectly:

 

For those of you having issues with installing it to an NVME m.2 drive, if you can get past the USB 3.0 driver issue, its not bad. I used Gigabyes usb driver injector on a Windows 7 ISO that I already had on on a USB thumbdrive. I had an extra SATA SSD sitting around so I tossed it in my system, installed Windows 7 to that, installed the Samsung 960 Pro drivers on the first boot, and cloned the drive over to the NVME ssd. After I used the patch that gets rid of the pesky "we dont support your cpu" bullshit, it was just fine.

 

Well, I also do Photoshop (good old CS3) and 3d rendering and I very seldom experience that more than 8GB is being used, so 128GB for this purpose sound like crazy overkill!!!! (Have been doing professional graphic design on PC since 1992, when 32MB was a lot of RAM...!)
I can only recommend G-Skill Flare-X, which works right out of the box on max speed - 3200GHz in my case. If you buy Corsair, you need a particular version, which is usually not visible when buying on-line - this is a recipe for disaster).

 

Hi everyone,

I'm trying to fight the Win10 current and install Win7 on my new Asus Prime X399-A mobo. Problem is I've only managed to succeed with MBR partition scheme, but what I want is to be able to install with GPT partition scheme and NTFS file system.
I'm unable to boot with the flash drive formated in GPT + NTFS.

A more detailed description of the problem and what I've tried so far can be found in a separate thread here

Any help would be appreciated!

 

Just install windows 10
Or install linux if you must. But just let windows 7 die already.

 

What's wrong with 7?

I think you need to slipstream NVMe drivers onto the 7 install?

 

It's not that, I've already done that and was successful otherwise I wouldn't have been able to install in MBR - Legacy mode.
I think it's BIOS related and I can't figure it out...

 

From what I understand, despite the fact that you were able to install in MBR / Legacy mode, NVMe does not support it and therefore, will not work. Just use GPT, which Windows 7 fully supports.

 

It's EOL in like a year. It's already not getting anything save for critical security updates. People are going to make Win 7 the new XP. As others have said just install Win 10 and move on unless you have some enterprise software that doesn't run on Win 10. We had a similar problem here @ work but we've moved onto Win 10 across the entire enterprise now.

 

Better to go to 8.1. than the abomination that is W10.

 

8.1 isn't exactly a fan favorite.