- Tile Database Is Corrupted 2004
- Windows 10 Tile Database Is Corrupt
- Tile Database Is Corrupt Infopackets
- Tile Database Is Corrupt
- The database file appears to have some corruption, this can happen due to disk or network issues or because of a power failure. Recommended Fix. If you are running version 18.1.38.0 or later, you can repair your database by running the relevant command in an administrative PowerShell window: pdqinventory RepairDatabase pdqdeploy RepairDatabase.
- Tile Database is Corrupt in build 17101 hi i cant change any settings on Start Menu and after restart all changes undo to default. I troubleshuted windows and founded Tile Database is Corrupt.
- What Is The ‘Windows 10 Tile Database Corrupt' Error? When you get these errors, the troubleshooter shows the error ' Tile database is corrupt '. The start menu tile files are stored in a database in the AppData folder. If somehow this database gets corrupted, the start menu stops working and the symptoms above start appearing.
Cause: Windows 10, version 1507 through the release of version 1607 uses a database for the Tile image information. This is called the Tile Data Layer database. (The feature was deprecated in Windows 10 1703.) Resolution There are steps you can take to fix the icons, first is to confirm that is the issue that needs to be addressed. The Tile repository is the database that stores your modern app settings, icons, references between the Name of the App and GUID etc. Anyone familiar with Exchange will be familiar with the EDB database and repairing corrupt edb files. I was very excited to see that it was in use here.
This just happened to me this morning, where after an update last night my Modern Apps icons were missing, the Start menu wouldn't load, right clicking was working sporadically and to add insult to injury -the task manager would hang when loading before closing itself out. Needless to say, this is NOT a situation you want to find yourself in.
5 Steps total
Step 1: Verify the issue is the same as described
Despite symptoms being very similar, make sure that the actual problem is the one that is described above -open Event Viewer and verify you have the following events listed.
Log Name: Application
Source: ESENT
Date: 11/22/2015 9:15:46 AM
Event ID: 465
Task Category: Logging/Recovery
Level: Error
Keywords: Classic
User: N/A
Computer: Mendy-THINK.glt.local
Description:
svchost (1812) TILEREPOSITORYS-1-5-21-970974742-2438072907-1744883273-1615: Corruption was detected during soft recovery in logfile C:Usersmendy.GLTAppDataLocalTileDataLayerDatabaseEDB.log. The failing checksum record is located at position END. Data not matching the log-file fill pattern first appeared in sector 320 (0x00000140). This logfile has been damaged and is unusable.
Event Xml:
465
2
3
0x80000000000000
30765
Application
Mendy-THINK.glt.local
svchost
1812
TILEREPOSITORYS-1-5-21-970974742-2438072907-1744883273-1615:
C:Usersmendy.GLTAppDataLocalTileDataLayerDatabaseEDB.log
END
320 (0x00000140)
Log Name: Application
Source: ESENT
Date: 11/22/2015 9:15:46 AM
Event ID: 477
Task Category: Logging/Recovery
Level: Error
Keywords: Classic
User: N/A
Computer: Mendy-THINK.glt.local
Description:
svchost (1812) TILEREPOSITORYS-1-5-21-970974742-2438072907-1744883273-1615: The log range read from the file 'C:Usersmendy.GLTAppDataLocalTileDataLayerDatabaseEDB.log' at offset 1310720 (0x0000000000140000) for 4096 (0x00001000) bytes failed verification due to a range checksum mismatch. The expected checksum was 5185428953563641081 (0x47f65828e12fb4f9) and the actual checksum was 1378623927485 (0x140fc63b4bd). The read operation will fail with error -501 (0xfffffe0b). If this condition persists then please restore the logfile from a previous backup.
Event Xml:
477
2
3
0x80000000000000
30764
Application
Mendy-THINK.glt.local
svchost
1812
TILEREPOSITORYS-1-5-21-970974742-2438072907-1744883273-1615:
C:Usersmendy.GLTAppDataLocalTileDataLayerDatabaseEDB.log
1310720 (0x0000000000140000)
4096 (0x00001000)
-501 (0xfffffe0b)
5185428953563641081 (0x47f65828e12fb4f9)
1378623927485 (0x140fc63b4bd)
Log Name: Application
Source: ESENT
Date: 11/22/2015 9:15:45 AM
Event ID: 454
Task Category: Logging/Recovery
Level: Error
Keywords: Classic
User: N/A
Computer: Mendy-THINK.glt.local
Description:
svchost (1812) TILEREPOSITORYS-1-5-21-970974742-2438072907-1744883273-1615: Database recovery/restore failed with unexpected error -501.
Event Xml:
Tile Database Is Corrupted 2004
454
2
3
0x80000000000000
30763
Application
Mendy-THINK.glt.local
svchost
1812
TILEREPOSITORYS-1-5-21-970974742-2438072907-1744883273-1615:
-501
Windows 10 Tile Database Is Corrupt
Step 2: Quick Explanation
The Tile repository is the database that stores your modern app settings, icons, references between the Name of the App and GUID etc. Anyone familiar with Exchange will be familiar with the EDB database and repairing corrupt edb files. I was very excited to see that it was in use here.
Step 3: Verifying Database
Tile Database Is Corrupt Infopackets
Using this article https://support.microsoft.com/en-us/kb/244525 I grabbed a copy of ESEUTIL and ran it against the AppDataLocalTileDataLayerDatabasevedatamodel.edb file. To my surprise the database was in clean shutdown mode, and the checksum was valid as well. (for those who do this on Exchange you can probably guess whats coming next)
Step 4: Remove the log files
Once the database is confirmed healthy, the log files are no longer required. Note that in most cases the log files can have some data that haven't been committed to the database -in these situations (MINOR) data loss can occur by deleting the log files. In this case, since the database is in Clean Shutdown and not Dirty Shutdown its unlikely that there's any data that hasn't been committed to the database.
While confident in my knowledge and this process when dealing with a Microsoft Exchange Mailbox Database, the bottom line is we're NOT dealing with an Exchange Server here -to be safe I made a New Folder and moved all files but the vedatamodel.edb file to it (outside of the Database directory)
Step 5: Reboot!
I'm not sure if this step is really necessary, since the corruption and issues exist solely inside the user profile, it's likely a simple logoff and logon is the only thing required -I did a reboot however because I wasn't really thinking about it. You'll notice an immediate difference in the amount of time it takes to login, for me it was significantly faster.
This just happened to me this morning, where after an update last night my Modern Apps icons were missing, the Start menu wouldn't load, right clicking was working sporadically and to add insult to injury -the task manager would hang when loading before closing itself out. Needless to say, this is NOT a situation you want to find yourself in.
5 Steps total
Step 1: Verify the issue is the same as described
Despite symptoms being very similar, make sure that the actual problem is the one that is described above -open Event Viewer and verify you have the following events listed.
Log Name: Application
Source: ESENT
Date: 11/22/2015 9:15:46 AM
Event ID: 465
Task Category: Logging/Recovery
Level: Error
Keywords: Classic
User: N/A
Computer: Mendy-THINK.glt.local
Description:
svchost (1812) TILEREPOSITORYS-1-5-21-970974742-2438072907-1744883273-1615: Corruption was detected during soft recovery in logfile C:Usersmendy.GLTAppDataLocalTileDataLayerDatabaseEDB.log. The failing checksum record is located at position END. Data not matching the log-file fill pattern first appeared in sector 320 (0x00000140). This logfile has been damaged and is unusable.
Event Xml:
465
2
3
0x80000000000000
30765
Application
Mendy-THINK.glt.local
svchost
1812
TILEREPOSITORYS-1-5-21-970974742-2438072907-1744883273-1615:
C:Usersmendy.GLTAppDataLocalTileDataLayerDatabaseEDB.log
END
320 (0x00000140)
Log Name: Application
Source: ESENT
Date: 11/22/2015 9:15:46 AM
Event ID: 477
Task Category: Logging/Recovery
Level: Error
Keywords: Classic
User: N/A
Computer: Mendy-THINK.glt.local
Description:
svchost (1812) TILEREPOSITORYS-1-5-21-970974742-2438072907-1744883273-1615: The log range read from the file 'C:Usersmendy.GLTAppDataLocalTileDataLayerDatabaseEDB.log' at offset 1310720 (0x0000000000140000) for 4096 (0x00001000) bytes failed verification due to a range checksum mismatch. The expected checksum was 5185428953563641081 (0x47f65828e12fb4f9) and the actual checksum was 1378623927485 (0x140fc63b4bd). The read operation will fail with error -501 (0xfffffe0b). If this condition persists then please restore the logfile from a previous backup.
Event Xml:
477
2
3
0x80000000000000
30764
Application
Mendy-THINK.glt.local
svchost
1812
TILEREPOSITORYS-1-5-21-970974742-2438072907-1744883273-1615:
C:Usersmendy.GLTAppDataLocalTileDataLayerDatabaseEDB.log
1310720 (0x0000000000140000)
4096 (0x00001000)
-501 (0xfffffe0b)
5185428953563641081 (0x47f65828e12fb4f9)
1378623927485 (0x140fc63b4bd)
Log Name: Application
Source: ESENT
Date: 11/22/2015 9:15:45 AM
Event ID: 454
Task Category: Logging/Recovery
Level: Error
Keywords: Classic
User: N/A
Computer: Mendy-THINK.glt.local
Description:
svchost (1812) TILEREPOSITORYS-1-5-21-970974742-2438072907-1744883273-1615: Database recovery/restore failed with unexpected error -501.
Event Xml:
Tile Database Is Corrupted 2004
454
2
3
0x80000000000000
30763
Application
Mendy-THINK.glt.local
svchost
1812
TILEREPOSITORYS-1-5-21-970974742-2438072907-1744883273-1615:
-501
Windows 10 Tile Database Is Corrupt
Step 2: Quick Explanation
The Tile repository is the database that stores your modern app settings, icons, references between the Name of the App and GUID etc. Anyone familiar with Exchange will be familiar with the EDB database and repairing corrupt edb files. I was very excited to see that it was in use here.
Step 3: Verifying Database
Tile Database Is Corrupt Infopackets
Using this article https://support.microsoft.com/en-us/kb/244525 I grabbed a copy of ESEUTIL and ran it against the AppDataLocalTileDataLayerDatabasevedatamodel.edb file. To my surprise the database was in clean shutdown mode, and the checksum was valid as well. (for those who do this on Exchange you can probably guess whats coming next)
Step 4: Remove the log files
Once the database is confirmed healthy, the log files are no longer required. Note that in most cases the log files can have some data that haven't been committed to the database -in these situations (MINOR) data loss can occur by deleting the log files. In this case, since the database is in Clean Shutdown and not Dirty Shutdown its unlikely that there's any data that hasn't been committed to the database.
While confident in my knowledge and this process when dealing with a Microsoft Exchange Mailbox Database, the bottom line is we're NOT dealing with an Exchange Server here -to be safe I made a New Folder and moved all files but the vedatamodel.edb file to it (outside of the Database directory)
Step 5: Reboot!
I'm not sure if this step is really necessary, since the corruption and issues exist solely inside the user profile, it's likely a simple logoff and logon is the only thing required -I did a reboot however because I wasn't really thinking about it. You'll notice an immediate difference in the amount of time it takes to login, for me it was significantly faster.
I spent most of my morning trying to find this answer, and haven't been able to find a reason or solution until I went back to eventvwr and found these errors. The lesson is, dont ever forget the basics! Event Viewer (at least for now) is still around despite the new fancy shell and modernized apps for Windows 10! Hurrah for the classic diagnostic procedures :)
Tile Database Is Corrupt
4 Comments
- Pimientocf8 Dec 22, 2015 at 06:20pm
So, using eseutil is great and all..but for those of us who no longer have (or never have had) access to an Exchange server..how exactly are we supposed to get ahold of Eseutil.exe, Ese.dll, Jcb.dll, Exosal.dll, and Exchmem.dll files? Looking at the page you reference, all I saw was a list of stuff Microsoft says to get off an Exchange server.
- Pimientomogensbjerg Jan 31, 2016 at 12:24am
Hi
I just had same problem.
Quick solution:
replace C:UsersUSER.BADAppDataLocalTileDataLayer catalogue
with
C:UsersUSER.OKAppDataLocalTileDataLayer catalogue from user on same machine that
have no problems.Best for downloading video and audio tracks from SoundCloud and many other websites. 🏆 The best SoundCloud To MP3 converter. Completely Free! We know the market. We know what users like you want. So we have created the perfect SoundCloud to MP3 converter. And what we have done has been to offer it totally free so that you can use it at all times without worrying about anything. Knowing that you are having such a good. Best soundcloud ripper. What is SoundCloud to Mp3? Soundcloud hosts a gigantic library of 125 million awesome songs. Perhaps, you want many of them in your device. If you are looking to convert soundcloud to mp3, then you are at the right place.We present to you the best way to convert them to mp3 so that they can get stored in your laptop, mobile, and computer.
Maybe you can create new user and copy from new account (I not tried)
AND PLEASE REMEMBER TO MAKE A BACKUP BEFORE YOU DO ANYTHING..
(Trust me.. It is a good idea.. I known ;-) - CayenneMendy Jan 31, 2016 at 12:45am
The detailed steps were really just to explain my thought process and how I got to this conclusion. You can just remove the log files and if it doesn't work replace the database with a copy from a good user. Chances are it will work.
- Pimientomichaelfreidgeim Apr 17, 2016 at 10:11am
Similar answer with steps see on thread http://answers.microsoft.com/en-us/windows/forum/windows_10-other_settings/corrupt-vedatamodeledb-issues/827bd69c-e6c5-4032-bbeb-cc282aa0e295?auth=1 MoltenTesseract answer on January 13, 2016
