Share via


svchost (3808) SRUJet: Database C:\Windows\system32\SRU\SRUDB.dat: Index UserIdTimeStamp of table {DA73FB89-2BEA-4DDC-86B8-6E048C6DA477} is corrupted (0).

Question

Friday, December 15, 2017 4:17 PM

This event was displayed in event viewer:

svchost (3808) SRUJet: Database C:\Windows\system32\SRU\SRUDB.dat: Index UserIdTimeStamp of table {DA73FB89-2BEA-4DDC-86B8-6E048C6DA477} is corrupted (0).

Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>chkdsk /scan
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
  471040 file records processed.
File verification completed.
  11672 large file records processed.
  0 bad file records processed.

Stage 2: Examining file name linkage ...
  578856 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  53909 data files processed.
CHKDSK is verifying Usn Journal...
  41253400 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

 731992063 KB total disk space.
 437941656 KB in 304519 files.
    193560 KB in 53910 indexes.
         0 KB in bad sectors.
    606855 KB in use by the system.
     65536 KB occupied by the log file.
 293249992 KB available on disk.

      4096 bytes in each allocation unit.
 182998015 total allocation units on disk.
  73312498 allocation units available on disk.

C:\Windows\system32>

Is this type of corruption detected or not detected by scannow?

Is this type of corruption detected or not detected by restorehealth?

Is this type of corruption detected or not detected by chkdsk?

How come in this case all of the above are not displaying any corruption?

Where is the corruption coming from?

What found the corruption?

How come it was reported?

What are the various options to fix the corruption?

How would this corruption manifest itself on the computer?

What does the is corrupted (0) 0 refer to?

What detects corruption of dat files?

All replies (1)

Monday, December 18, 2017 6:46 AM | 1 vote

Hi,

This error can occur in an unexpected system crash forcing a full disk restore. Also it refers to Diagnostic Policy Service.

SRUJet is a database engine working with database file srudb.dat.

  • You should be safely able to delete srudb.dat and Windows should re-create it.
  • The functionality is part of Diagnostic Policy Service.

You can post permissions of the file for further details.

If the issue still insists, I consider it could be caused with hardware.

Hope it will be helpful to you

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].