I have well over the recommended specs but i am getting the warning for not meeting them. I have updated my drivers and checked others and verified the game files but i am still getting the warning.
Minimum requirements not met lies
Reported
Hi. I've been getting a warning about minimum requirements not being met when I launch the game. I'm running an AMD Ryzen 9800x3d, an RTX 5080, and 64 gigs of ram. I don't know in what universe that is below minimum specs. Here's an exerpt from the logs; it seems to have an issue detecting my drive, which it complains about for some reason:
2025-12-06 13:55:46.190 - Main Thread -> LogEnvironmentInformation - START
2025-12-06 13:55:46.194 - Main Thread -> Win32_ComputerSystem.Manufacturer: Gigabyte Technology Co., Ltd.
2025-12-06 13:55:46.194 - Main Thread -> Win32_ComputerSystem.Model: B650M AORUS ELITE AX ICE
2025-12-06 13:55:46.199 - Main Thread -> Virtualized: False
2025-12-06 13:55:46.202 - Main Thread -> Environment.ProcessorName: AMD Ryzen 7 9800X3D 8-Core Processor
2025-12-06 13:55:46.202 - Main Thread -> ComputerInfo.TotalPhysicalMemory: 66,158,145,536 bytes
2025-12-06 13:55:46.202 - Main Thread -> ComputerInfo.TotalVirtualMemory: 140,737,488,224,256 bytes
2025-12-06 13:55:46.202 - Main Thread -> ComputerInfo.AvailablePhysicalMemory: 42,725,261,312 bytes
2025-12-06 13:55:46.202 - Main Thread -> ComputerInfo.AvailableVirtualMemory: 138,256,240,742,400 bytes
2025-12-06 13:55:46.206 - Main Thread -> Drive C: | Capacity: 2,047,730,511,872 bytes | Free space: 1,865,083,551,744 bytes
2025-12-06 13:55:46.206 - Main Thread -> Drive D: | Capacity: 4,000,762,032,128 bytes | Free space: 3,637,179,613,184 bytes
2025-12-06 13:55:46.206 - Main Thread -> Drive E: | Capacity: 480,101,003,264 bytes | Free space: 320,925,216,768 bytes
2025-12-06 13:55:46.852 - Main Thread -> [Windows System Helper]: No partitions found for path D:\Games\Steam\steamapps\common\SpaceEngineers2\Game2\SpaceEngineers2.exe. Cannot proceed detecting the drive.
2025-12-06 13:55:46.853 - Main Thread -> [Crash Handler] : [Process Tag Added] : MinRequirementsNotMet
2025-12-06 13:55:46.853 - Main Thread -> LogEnvironmentInformation - END
I have the same bug
Hello Austin Berry,
According to the logs you've provided, the Game could not determine the physical drive that the game is installed on. Space Engineers 2 performs a hardware / storage check on startup, including identifying the physical drive type (SSD/HDD). This is used for minimum requirement validation.
Since the physical drive could not be determined, the Minimum Requirements not met warning popped up.
If you could tell me what type of drive you are using for SE2 installation, I may be able to assist further.
Kind Regards,
Bartosz
Keen Software House
Hello Austin Berry,
According to the logs you've provided, the Game could not determine the physical drive that the game is installed on. Space Engineers 2 performs a hardware / storage check on startup, including identifying the physical drive type (SSD/HDD). This is used for minimum requirement validation.
Since the physical drive could not be determined, the Minimum Requirements not met warning popped up.
If you could tell me what type of drive you are using for SE2 installation, I may be able to assist further.
Kind Regards,
Bartosz
Keen Software House
im going to guess its nvme drive that it cant find? i also have a 4tb drive its not able to find and a few others here have drives larger than 2tb that it cant find
im going to guess its nvme drive that it cant find? i also have a 4tb drive its not able to find and a few others here have drives larger than 2tb that it cant find
I have a work around
make a new virtual hard drive it can be on your nvme drive just make sure its a new simple volume and NTFS. Initialise the drive. you can do this by going to disk management then up at the top Action > Create VHD. a small box will pop it will ask for a location to place the drive, and as i said before this can be on your dynamic nvme it will be fine. under that it will ask for size SE2 doesn't need a ton of space but i would give it a bit of headroom for later updates (se2 is just under 41GB currently and the SDK is just under 97GB)
keep it at fixed size and click ok, it will take a few mins to create you will see a progress bar at the bottom of the Disk Management window. Once created it will be black and unallocated. just right click and initialise it, choose its name ect
you can check its right by doing CMD > DISKPART > LIST DISK and it should be something like the attached image.
then just go on steam and move SE2 (and the SDK if you use that) to your new virtual drive. it will now work.
I have a work around
make a new virtual hard drive it can be on your nvme drive just make sure its a new simple volume and NTFS. Initialise the drive. you can do this by going to disk management then up at the top Action > Create VHD. a small box will pop it will ask for a location to place the drive, and as i said before this can be on your dynamic nvme it will be fine. under that it will ask for size SE2 doesn't need a ton of space but i would give it a bit of headroom for later updates (se2 is just under 41GB currently and the SDK is just under 97GB)
keep it at fixed size and click ok, it will take a few mins to create you will see a progress bar at the bottom of the Disk Management window. Once created it will be black and unallocated. just right click and initialise it, choose its name ect
you can check its right by doing CMD > DISKPART > LIST DISK and it should be something like the attached image.
then just go on steam and move SE2 (and the SDK if you use that) to your new virtual drive. it will now work.
I have a work around
make a new virtual hard drive it can be on your nvme drive just make sure its a new simple volume and NTFS. Initialise the drive. you can do this by going to disk management then up at the top Action > Create VHD. a small box will pop it will ask for a location to place the drive, and as i said before this can be on your dynamic nvme it will be fine. under that it will ask for size SE2 doesn't need a ton of space but i would give it a bit of headroom for later updates (se2 is just under 41GB currently and the SDK is just under 97GB)
keep it at fixed size and click ok, it will take a few mins to create you will see a progress bar at the bottom of the Disk Management window. Once created it will be black and unallocated. just right click and initialise it, choose its name ect
you can check its right by doing CMD > DISKPART > LIST DISK and it should be something like the attached image.
then just go on steam and move SE2 (and the SDK if you use that) to your new virtual drive. it will now work.
I have a work around
make a new virtual hard drive it can be on your nvme drive just make sure its a new simple volume and NTFS. Initialise the drive. you can do this by going to disk management then up at the top Action > Create VHD. a small box will pop it will ask for a location to place the drive, and as i said before this can be on your dynamic nvme it will be fine. under that it will ask for size SE2 doesn't need a ton of space but i would give it a bit of headroom for later updates (se2 is just under 41GB currently and the SDK is just under 97GB)
keep it at fixed size and click ok, it will take a few mins to create you will see a progress bar at the bottom of the Disk Management window. Once created it will be black and unallocated. just right click and initialise it, choose its name ect
you can check its right by doing CMD > DISKPART > LIST DISK and it should be something like the attached image.
then just go on steam and move SE2 (and the SDK if you use that) to your new virtual drive. it will now work.
Devs, pleaser add a check box to not show again. Super simple, should have been there from the start. That is true for any kind of soft alert like this.
Devs, pleaser add a check box to not show again. Super simple, should have been there from the start. That is true for any kind of soft alert like this.
Can confirm, I see this on Linux too. figured it was a proton thing but to see it happening on windows and is attributed to the storage type and capacity, that just seems kinda weird. there needs to be a way to ignore it. game runs fine regardless.
Can confirm, I see this on Linux too. figured it was a proton thing but to see it happening on windows and is attributed to the storage type and capacity, that just seems kinda weird. there needs to be a way to ignore it. game runs fine regardless.
Also linux with proton, game runs fine, vastly exceed minimum specs. Kinda dumb. Code needs to specify on error to skip the notification. If you sitting with a crappy 8G vid card and you know it sure pop the alert. If you can't tell what something is than just assume it is better and reporting/faking weird; continue on.
Also linux with proton, game runs fine, vastly exceed minimum specs. Kinda dumb. Code needs to specify on error to skip the notification. If you sitting with a crappy 8G vid card and you know it sure pop the alert. If you can't tell what something is than just assume it is better and reporting/faking weird; continue on.
Hello Johan Stenqvist,
This is a known issue that is already reported internally. I have added this thread to our internal ticket (SE2-29395).
Kind Regards,
Bartosz
Keen Software House
Hello Johan Stenqvist,
This is a known issue that is already reported internally. I have added this thread to our internal ticket (SE2-29395).
Kind Regards,
Bartosz
Keen Software House
Replies have been locked on this page!