this post was submitted on 04 Mar 2026
-1 points (33.3% liked)

Windows 11

1169 readers
7 users here now

Welcome to the community for Windows 11, Microsoft's latest computer operating system.

Rules:

founded 2 years ago
MODERATORS
 

nvraid.sys nvstor.sys

top 3 comments
sorted by: hot top controversial new old
[–] TheFinn@discuss.tchncs.de 2 points 1 day ago

Why would you delete them?

[–] chickenf622@sh.itjust.works 1 points 1 day ago

Usually a good idea to leave files in system32 alone unless you know exactly what it does. It's possible the drivers are being used for something else that just happens to use drivers provided by NVidia (assuming those files are indeed related to NVidia). I also doubt they're taking up that much space on your drive.

[–] wizardbeard@lemmy.dbzer0.com 1 points 1 day ago* (last edited 1 day ago)

No. Don't fuck with the contents of system 32.


Edit: You're the guy that thought windows broke his USB functionality to force an update.

If you were fucking with the contents of system32, you broke your USB functionality (and caused the blue screen) yourself.

Those are the files that Windows uses to run. Don't fuck with them if you want Windows to keep running.

I have 5 years of experience in tech support in a Windows environment, then 5 years of system administration and engineering also in a Windows environment. Plus years of being a computer nerd before it became my career.

I think in all that time I've only ever had reason to delete files in system32 directly around 5 times. There used to be a bug with one specific log folder where it could bloat up over multiple GB, but that was fixed many years ago, and it was a well known issue.

Any other time I've made changes to system32 it has been effectively by proxy. Installing fonts, adjusting group policy settings that have further effects (normally they just adjust registry), installing and uninstalling some of the few programs that touch those folders.


In short, 999 time out of 1000, you're better off leaving system32 the fuck alone.

If you want to mess around with shit that likely to break your computer, make a VM and go nuts. Don't do it on a machine you rely on having work properly.