Question System Can Not Create New sru or sruJET Folder for Errors

DJLegacy2k5

Prominent
Dec 15, 2019
16
0
510
0
So,

My PC is throwing 32,000 errors a day mainly at boot because it wants to make a new sru and sruJET folder in Windows then System32 but it cant because the entire directory is "read only". I have followed EVERY trick and or hack and article blaming this on Windows updates, used a tool to "take back ownership", gave everything on my PC FULL access since I'm the only one using the PC, I've used cmd line commands to change the system permissions as they say, I have followed all 20 plus fixes for this, made sure anti virus was blocking "sensitive file folders" I mean, everything I could find for fixes....nothing.....I can make a folder caller sru in there but it doesnt matter as Windows appare tly cant write to it's own Windows folders.....

What so I do here so i can stop having 32,000 errors in event viewer saying "can not write to folder because the drive is read only".

I'm so severely irritated at this point. I dont want to di ANOTHER install of windows and then reinstalling the 1000 deleted programs at that time. I dont want to copy, save or clone any thing to do with the drive because I tried that I cloned windowsnfrom a 480GB ssd to a 1tb nvme as a test and everything is still bad..

What can I do, all help appreciated!

-DJ
 

USAFRet

Titan
Moderator
Mar 16, 2013
140,201
7,645
174,040
21,599
You don't fix/change the "read only" thing....you fix the cause of it trying to throw these errors.

https://social.technet.microsoft.com/Forums/en-US/e124413a-8c14-444d-944a-429fd23d9381/svchost-3808-srujet-database-cwindowssystem32srusrudbdat-index-useridtimestamp-of-table?forum=win10itprogeneral


What actual fixes have you tried?
sfc /scannow, for instance.

And DISM - https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

And cloning is not the thing here.
Cloning a problematic install just means moving the problem to a different drive.
 

DJLegacy2k5

Prominent
Dec 15, 2019
16
0
510
0
You don't fix/change the "read only" thing....you fix the cause of it trying to throw these errors.

https://social.technet.microsoft.com/Forums/en-US/e124413a-8c14-444d-944a-429fd23d9381/svchost-3808-srujet-database-cwindowssystem32srusrudbdat-index-useridtimestamp-of-table?forum=win10itprogeneral


What actual fixes have you tried?
sfc /scannow, for instance.

And DISM - https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

And cloning is not the thing here.
Cloning a problematic install just means moving the problem to a different drive.
I knew cloning wasnt the right thing but I wanted to move things to the nvme as I'm doing lots of work in Unreal Engine 4.26 and I'm gopong this Evo 970 plus nvme and new 980 Pro nvme will help speed things up & the new Samsung QVO 4T will e about z nkf f'
Create those folders and on them
set owner to SYSTEM,​
give SYSTEM and Administrators full control.​
Did this no worky
 

DJLegacy2k5

Prominent
Dec 15, 2019
16
0
510
0
You don't fix/change the "read only" thing....you fix the cause of it trying to throw these errors.

https://social.technet.microsoft.com/Forums/en-US/e124413a-8c14-444d-944a-429fd23d9381/svchost-3808-srujet-database-cwindowssystem32srusrudbdat-index-useridtimestamp-of-table?forum=win10itprogeneral


What actual fixes have you tried?
sfc /scannow, for instance.

And DISM - https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image

And cloning is not the thing here.
Cloning a problematic install just means moving the problem to a different drive.
The cause was the sru folder got deleted...by me because one of these nice tech sites said once you delete thenfoldwr thebaystencwill recreate....they were right, MANY other people said the solder and all was rebuilt.....mine, not so much I've given SYSTEM and my account FULL control...still no worky
 

ASK THE COMMUNITY

TRENDING THREADS