New Windows 10 Insider Preview Fast+Slow Build 18362 (19H1) - Mar. 22 Insider

Dave44 said:

sandbox only on pro and enterprise versions

yes.

°

kado897 said:

yes.

What about Education?

Zardoc said:

I'm seeing an Esent error but so far start menu hasn't reacted nor any tiles. It's more of an event viewer issue.

ESENT Event ID 455
svchost (11216,R,98) TILEREPOSITORYS-1-5-18
C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log.

OK, I found the reason for the error. The folder doesn't exist. It tries to find it but it's not there.

C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log

Mind you, this isn't a clean install. It's an upgrade. Might not show up on clean install.

Zardoc said:

OK, I found the reason for the error. The folder doesn't exist. It tries to find it but it's not there.

C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log

Mind you, this isn't a clean install. It's an upgrade. Might not show up on clean install.

I was getting exactly the same error as that with the path C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log the same as yours.
All I did was create the folder TileDataLayer and inside that created another folder Database. The database directory was left empty and I restarted the PC. A few minutes after the restart I checked the Database folder and it had been populated by a file EDB.log plus a couple of others.
Result was rhat the ESENT error went away and has stayed away.

DooGie said:

I was getting exactly the same error as that with the path C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log the same as yours.
All I did was create the folder TileDataLayer and inside that created another folder Database. The database directory was left empty and I restarted the PC. A few minutes after the restart I checked the Database filder and it had been populated by afile EDB.log plus a couple of others.
Result was rhat the ESENT error went away and has stayed away.

Hi Doogie,

That's also what I did. I was waiting to see if it populated. Just checked, yep, it's populated.

Thanks.

Zardoc said:

Hi Doogie,

That's also what I did. I was waiting to see if it populated. Just checked, yep, it's populated.

Thanks.

The only problem is that when the next build is released the two directories get wiped so you have to do it again. I've had the same with the last three builds.

DooGie said:

The only problem is that when the next build is released the two directories get wiped so you have to do it again. I've had the same with the last three builds.

I've been keeping for myself a log for a couple of years. Every time a new build is out I try to find the errors that show up in an upgrade vs a clean install. Then I either make command lines or reg tweaks to correct the problems.

For instance, upgrades of 1803 showed user profile errors. The fix was to get rid of some registry lines (TDL).

I just noticed the blurred lock screen for 1903 and applied Shawn's reg tweak and added it to my journal for my friends and customers.

It would be nice if like the tutorials there was a section for known bugs and temporary or permanent fixes.

Weekly Windows 10 Insider Program Pulse #61 Survey