Share via

User Profile Service Event 1534

Question

Wednesday, August 1, 2018 9:33 PM | 9 votes

Since build 17711 (also on latest 17728) all of my user accounts logs User Profile Service Event 1534 continiously (several times per minute). Even on a brand new non-domain account. Everything seems to work fine, but would be nice to understand this error?

Profile notification of event Load (and Unload) for component {B31118B2-1F49-48E5-B6F5-BC21CAEC56FB} failed. Errorcode: See Tracelogging for error details.

Kind regards
Kasper

All replies (66)

Thursday, August 2, 2018 9:16 AM

Hi Kasper,

First of all, your opinion is connect. This is a warn level event and won't affect your usage. Please just ignore it.

Furthermore, Please log on as an administrator, launch regedit and change the ProfileImagePath value in the key that ends in ".bak" to match the actual profile folder name.  Alternatively, you can change the name of the profile to match the ProfileImagePath value in the key that ends in ".bak".  After you fix the mismatch, change the key name that does not have ".bak" in it by adding an extension such as ".old".  Then remove the ".bak" extension from the correct profile key.

In addition, check if your domain account belongs to Domain Guest group. If yes, remove it.

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

Friday, August 3, 2018 6:56 AM | 1 vote

Hi Karen.

Thanks for your reply.

There is no .bak key in my registry. And the account is not a member of domain guests.

If a create a brand new (local) account the error is still logged.

Monday, August 6, 2018 4:12 PM | 2 votes

I am having the same issue on insiders build 17728 and it IS greatly impacting performance when opening most any new process. Opening a File Explorer new Window, Opening the Event Log, etc.

This is not happening on my non-insiders build of Windows 10.

The following error message appears 100's of times.

Profile notification of event Load for component {B31118B2-1F49-48E5-B6F5-BC21CAEC56FB} failed

Can you provide additional guidance? Please use detailed and specific responses. Don't assume I know what part of the registry to modify.

Thanks in advance. 

Mark

-- UPDATE --

I still have this issue but my performance issue was caused by a corrupt WMI which happened after last window insiders build update. I rebuilt the WMI to correct the performance problems. Here is a link to the procedure I used to rebuild WMI: https://social.technet.microsoft.com/Forums/windowsserver/en-US/8ed26d46-9994-4052-a307-5b071805aea8/wmi-corrupt-how-to-reinstallrepair

--

Wednesday, October 3, 2018 3:58 AM

The ProfileImagePath value points to the right directory and my profile is not part of the Domain Guest group.  This issue began right after updating to 1809.

Wednesday, October 3, 2018 7:34 AM | 2 votes

I am having the same problem after upgrading to Windows 10 Pro 1809 64 bit.  The ProfileImagePath value is correct.  I am logging in as Administrator.

Thank you for help.

Wednesday, October 3, 2018 2:37 PM | 2 votes

Lo and behold, same problem after upgrade from 1803 to 1809 home edition.

It seems to trigger mostly when you need to use anything that requires even in the slightest your admin account profile access.

Like starting CMD as admin, it all works mind you, but it will give off load and unload eventid 1534 3 or 4 times in a row.

I only have an admin account, no other accounts have ever existed on this system so i doubt there is any form of a mismatch.

No other problems though, infact it solved a few issues i had before. (spellchecker and dcom errors are all gone now)

But now it gets just swamped with eventid 1534, which i know i can safely ignore.. but clearly this is due to windows 10 1809 borking something up.

Can you please let someone at MS know so they can look at it? i have no idea how to do that myself other then reporting the issue here.

Wednesday, October 3, 2018 3:26 PM | 1 vote

Same issue here after downloading win 10 October update, tons of 1534 errors and cant find any solutions :\ P.S. Using only one administrator account.

Hope microsoft fix it soon.

Wednesday, October 3, 2018 3:39 PM

Well a reboot seemed to have made it go away actually.

First i tried simply off and on, that didnt help.

Now i've tried reboot, i did get em during the reboot, but now thats its rebooted i cant replicate it.

If i start apps or games or edge or whatever, normally i'd see 3 or 4 messages, that doesnt happen now for some reason.

However i dont know if thats due to rebooting, cause that is slightly different from literally turning the system off and on again.

Nvm, if i use anything now that does use my admin account, its back.

Also if i dont touch my mouse for a while and use it, 3 events, probably not the mouse itself but rather the whole user profile service thing kicking in.

Damnit.

Still it seems less severe then before.

2nd edit : checked the profile list in regedit : profileimagepath is correctly linked to the correct username (well there can be only one anyway lol)

maybe the culprit is C:users and perhaps the default map?

I've read that on tenforums somewhere, but thats going beyond my know-how.

3rd edit : using regedit to look up the GUID : B31118B2-1F49-48E5-B6F5-BC21CAEC56FB

It refers to the tileobjserver ..

This looks more and more like a bug on Microsofts end incl, how to fix it.

Thursday, October 4, 2018 7:52 AM | 1 vote

Does anyone know which guid its listed as under wmi autologger? As i could at least flag it so it doesnt keep reporting it.

The GUID the eventviewer lists, isnt listed for the autologger..

Also i wish we'd get a bit more help over here.

Thursday, October 4, 2018 8:12 PM | 3 votes

re: 1809 same issue on win 10 home … Karen_hu admin's suggestion does not help, but…

There are several ProfileImagePath keys in the registry, none of them seem to have any problem

Only the key that starts with S-1-5-21- contains a computer name ( nza_h ) that was previously given by an earlier built of windows (1706?). Though I did not rename it, even did not look at it, after installing 1809 it does not seem to exist any more. My pc uses a code name - also given by windows earlier built - but it does not match what is in the registry (nza-h)

There in no .bak file in the entire registry.

I use only one admin profile on my pc.

Friday, October 5, 2018 5:45 AM | 3 votes

Having the same damn issue drives me nuts component B31118B2-1F49-48E5-B6F5-BC21CAEC56FB event 1534 have no idea what to do

Friday, October 5, 2018 9:54 AM | 3 votes

Well looks like the problem, as i already stated, is the tileobjserver, which is related to the tiledatasvc.

Now that last one, has been removed from 1809, its no longer a "feature".

However, quite obviously the registry and some components were still left behind and they are still trying to do their thing, which it cant without the tiledatasvc being active or even having permission.

So you end up seeing basicly attempts to call on the service and "load and unload" data based on the user profile service, but it cant.

It IS safe to ignore i'd say in this case, but damn annoying.. i'd presume MS will come with a patch but kinda depends whats high on their list right now.

As there are more similar issues related to the user profile. (service but also folders like C:users and the default and other maps gone missing incl, all videos photos etc)

Which could also be related to this problem in some way.

Very sloppy update, as this exact problem was present in the insider preview version.

Friday, October 5, 2018 12:59 PM | 2 votes

Looks like a widespread problem, all the PC's I've updated have this error.  Get it together Microsoft.

Friday, October 5, 2018 6:45 PM | 1 vote

me too!

Friday, October 5, 2018 8:21 PM | 1 vote

Here to say I have the same issue. 

Friday, October 5, 2018 9:11 PM | 2 votes

I have the same events.
But I fear they are never gonna fix this.
There are events logged as error since Windows 8:
DCOM event ID 10016 is logged in Windows
still not fixed.

Monday, October 8, 2018 4:40 PM | 1 vote

Same issue here - BUT on all upgraded Win10 pro 1809 machines, yet only affecting SOME users.

The warning is there, but  some users always get on others do not.

Profile notification of event Load for component {B3xxxxxxxxFB} failed, error code is See Tracelogging for error details. 

Stuart

Wednesday, October 10, 2018 12:55 PM | 1 vote

Same problem, I guess there is no fix for this yet?

Wednesday, October 10, 2018 3:47 PM | 1 vote

Same problem here after updating to Windows 10 Version 10.0.17763 Build 17763:

Ereignis 1534, User Profile Service

Fehler bei der Profilbenachrichtigung des Ereignisses Load für Komponente {…}. Fehlercode: See Tracelogging for error details.

Thursday, October 11, 2018 9:20 PM

I do have the same issue after upgrading from 1803 to 1809.

Saturday, October 13, 2018 9:53 AM

No fix, you can do it manually, but even I.. and i do know sort of how its supposed to be done, rather not do it.

But essentially you'd have to take "control" as in give your account rights, and take over 2 registry keys that are causing this and simply delete them.

You could export them before you do it, but yeh its not one of those things that is comfy..

Saturday, October 20, 2018 5:36 PM

Can Extensible Counter List (exctrlst) be used to ignore these Application warnings? What's the name of the applicable Extensible Performance Counter? Thanks for any feedback.

Tuesday, October 23, 2018 5:30 PM | 1 vote

Just want to add my name to the list of people having multiple warning event errors, Code 1534, "Profile notification of event Load for component {B31118B2-1F49-48E5-B6F5-BC21CAEC56FB} failed, error code is See Tracelogging for error details", since recent update to Version 1809. Hope Microsoft comes out with a fix, and if more reports are made on this issue, maybe they will !

Wednesday, October 24, 2018 4:59 PM | 23 votes

Finally found a FIX for 1534 error !

1. Open Regedit and navigate to the following two keys
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileNotification
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\ProfileNotification
2. Under ProfileNotification check if you have the TDL key
3. Export the TDL key at each location
4. Delete the TDL key at each location
5. Reboot PC to verify

Note:
You'll need take ownership of the TDL Key to be able to delete it.

Works for me like a charm with no downsides.

After this fix the 1534 baragge has stopped in my OS :)

Thursday, October 25, 2018 6:06 PM | 1 vote

Thank you Sevenmm1985. The fix you outlined worked for me.

Friday, October 26, 2018 10:22 AM

Glad to help

Friday, October 26, 2018 10:27 AM

yes, correct procedure.
I also deleted the reference keys reported by the event manager.
now everything is ok

Monday, October 29, 2018 3:21 PM

Can you please explain how you took ownership of this key?

Ron Stransky

Monday, October 29, 2018 10:22 PM

  1. Right-click on the key, select Permissions.
  2. In the permissions for.. dialog, click the Advanced button, then click the "Change" link in the Advanced Security Settings dialog.
  3. Enter your domain\username in the edit box, click Check names and ensure it finds your name
  4. Click OK

You should be able to delete the key at that point. If it doesn't want to, try deleting each item in the key, then the key itself.

Saturday, November 3, 2018 6:02 PM

Wonderful.  No more 1534 errors and I am a real novice when it comes to registry editing.  Now - at what point can I delete those exported keys?  Hope future MS Updates won't require the old TDL keys.

Monday, November 12, 2018 10:28 PM

how do i take the ownership of the TDL key ?

Sunday, November 18, 2018 5:39 PM

yes, correct procedure.
I also deleted the reference keys reported by the event manager.
now everything is ok

Can you give more detail on what reference keys you deleted?

Friday, November 23, 2018 9:53 PM

well done! sevenmm it worx

my mount of reds had gone, too

i wish i new what TDL key was 

needed to change privileges though as described below

THX folks 

Sunday, November 25, 2018 4:38 PM

The TDL or TLD? (forgot already lol) keys were connected to the tile data service.

The tile data service was a service for your start menu for the live tiles updates and such.

But that service was removed back in 1803, for some reason the keys were left behind and the 1809 update (which is a massive flop really) made a deal out of it by getting all messy with it.

I've also removed them some time ago, though its wise to export them first.

There are no downsides i can see, so far.. ofcourse this is MS and windows we're talking about so who knows.

Wednesday, November 28, 2018 12:24 AM

Unfortunately, the fix by Sevenmm1985 did not work for me. I only found a TDL key at the first of the 2 given locations. I went ahead and deleted it (forgot to export first, hopefully won't end up biting me). Expected to find another at second location, but not there . . have triple-checked. I have the same steady stream of 1534's as I did before deletion.

I am glad that it seemed to have worked for everyone else, but also worrying why it does not work for me. All I can think of now is to maybe put back both TDL keys (don't even know if this is possible, especially since I forgot to export the key I did have) and reboot, maybe use the machine a bit, and then try deleting both keys. 

I also see that draffaele1972 reports deleting the reference keys reported by event manager. I don't know exactly which keys those are. If anybody can help with specification, I would appreciate it very much. And I will make sure to export first, this time!

Wednesday, November 28, 2018 2:42 PM | 1 vote

Deletion is not our method.
You just need to change the logging level. I put it by analogy with the "Group Policy" service - GPSvc.
Events = 0x3

Thursday, November 29, 2018 12:21 PM

 Yes, you are right. It is not our job to delete regedit. 1809 is not yet available in windows 10 automatic update. but with the help of the windows update assistant, I downloaded it to try out 1809 and was seamlessly installed on the existing system. but since I was experiencing this error, I had to go back to 1803 via the system image. because in each process, the windows always give three event errors. It's an annoying situation. I think 1809 still not OK . especially if the user alone with these problems. The solution of such problems should never erase regedits. 

Friday, December 7, 2018 4:02 PM

Haven't viewed the thread in quite sometime on this continuing nuisance event viewer warning, but used your clearly explained fix, and while initially I ended up with new error coded 1005... "DCOM got error "1115" attempting to start the service SecurityHealthService with arguments "Unavailable" in order to run the server:", found that after clearing error logs in event viewer, and shutting down computer, that on restart, found no errors and no Warning code 1534, logged on the Event Viewer. Will keep the saved TDL keys for awhile, but believe this fix will prove to be a 'good' fix and eliminate the  logging of 5-10 Warning errors, code 1534, on every restart. Thank you  Sevenmm1985 for passing the information along !

Tuesday, December 18, 2018 5:26 PM

>You'll need take ownership of the TDL Key to be able to delete the TDL Key.

I took ownership of both TDL keys, but still unable to delete them. It says "Cannot delete TDL: Error deleting key". "Error deleting values" comes also if I try to delete each item in the key first.

Wednesday, December 19, 2018 5:44 PM

If you do not want to take ownership of the keys you can just hide the event. Path is:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-Application\89b1e9f0-5aff-44a6-9b44-0a07a7ce5845}

Under enabled edit to make reg dword 0. You will no longer see the event in event viewer. I have the key in the registry. Some may not have it and will need to do the other fix.

Be aware though you will be hiding event 1534 from event viewer for good unless you change it back.

Wednesday, December 19, 2018 6:19 PM

>I took ownership of both TDL keys, but still unable to delete them. It says "Cannot delete TDL: Error >deleting key". "Error deleting values" comes also if I try to delete each item in the key first.

Finally I was able to delete TDL keys when the Full Control in permissions for SYSTEM was allowed in the keys.

Friday, December 28, 2018 8:32 AM

you are a god, for some reason at every load and unload event windows would play the usb disconnect sound so you have saved me my sanity

Sunday, January 6, 2019 3:19 AM

"Furthermore, Please log on as an administrator, launch regedit and change the ProfileImagePath value in the key that ends in ".bak" to match the actual profile folder name.  Alternatively, you can change the name of the profile to match the ProfileImagePath value in the key that ends in ".bak".  After you fix the mismatch, change the key name that does not have ".bak" in it by adding an extension such as ".old".  Then remove the ".bak" extension from the correct profile key.

In addition, check if your domain account belongs to Domain Guest group. If yes, remove it."

TOO COMPLICATED. MAKE STEP BY STEP VIDEO.

Look... I pay full price to have a working windows. I am the sole user of my PC and log in as Admin.

the steps you mention I could not get it done. I did not pay for a beta who I need to troubleshot myself.

Wednesday, January 9, 2019 7:52 PM

"Furthermore, Please log on as an administrator, launch regedit and change the ProfileImagePath value in the key that ends in ".bak" to match the actual profile folder name.  Alternatively, you can change the name of the profile to match the ProfileImagePath value in the key that ends in ".bak".  After you fix the mismatch, change the key name that does not have ".bak" in it by adding an extension such as ".old".  Then remove the ".bak" extension from the correct profile key.

In addition, check if your domain account belongs to Domain Guest group. If yes, remove it."

TOO COMPLICATED. MAKE STEP BY STEP VIDEO.

Look... I pay full price to have a working windows. I am the sole user of my PC and log in as Admin.

the steps you mention I could not get it done. I did not pay for a beta who I need to troubleshot myself.

That person you seem to be yelling at is not some Microsoft employee here to support you lol

You do not pay Microsoft for support. You paid them for a working product, and you got it. You chose to update; sometimes updates don't go exactly as planned. Now you're here yelling at the people who are only trying to help others, demanding they make you a video because you're too slow to follow simple instructions?

Get over yourself, internet stranger.

P.S. - Please don't take this out on your kids.

Saturday, January 12, 2019 4:59 AM

I had no clue how to do any of this and the 1534 event has been causing random freezing in games for about a week or two driving me mad. I pinned it down to the 1534 event because it was literally the only consistent thing happening every single time I got a freeze.

Anyway, I made an account just to tell you that you are THEE man and saved me from doing a full system wipe that I was about 10 minutes away from doing. Thank you!!

Saturday, January 12, 2019 5:01 AM

I came to this tread knowing how to do absolutely none of this and figured it out in about 5-10 minutes. Read. Everything you need to know is in the thread and you literally just need to follow file paths and click on what they said to click. 

Tuesday, January 15, 2019 12:55 AM

I find the problem exists on an upgrade from 1803, but does not occur on a clean install [used diskpart > clean and then did an install on a computer that originally had Windows 7 Pro on it.  UPgrades seem to have the issue though

Friday, January 18, 2019 3:25 AM

Hi Sevenmm1985,

I take following your guide but can not resolve

thanks 

Tuesday, January 22, 2019 3:51 PM

Hi

Would a registry cleaner such as ccleaner remove the unused registry keys?

Wednesday, January 23, 2019 5:07 PM

I have the same issue here but a bit wary about messing with the Registry . . does "4. Delete the TDL key at each location" mean delete the TDL folder completely or just the CLSID in the folder . . what exactly is the "key"? . . .

Wednesday, January 23, 2019 5:10 PM

You could simply ignore the error.

Wednesday, January 23, 2019 5:59 PM

I now understand it;s the folder that's the Key and inside there are "Registry Values" but now it won't delete the key but only says "Can't delete TDL: Error while deleting key"  . . and no reason for the error. but I found a youtube video to fix permissions so we will test this 1534 fix finally

Saturday, January 26, 2019 11:08 AM

Microsoft needs to get this fixed, given the replies here. None of this Regedit, bla bla bla which is a little dodgy for those who have no wish to attempt it themselves and ending up with a worse problem.

Sunday, January 27, 2019 7:06 PM

To erase the thousands of 1534 errors that accumulate in the event viewer, I just run the cmd as the administrator and paste this text into it. all accumulated 1534 and others wiping

for /f "tokens=*" %1 in ('wevtutil.exe el') do wevtutil.exe cl "%1"

Monday, February 11, 2019 6:57 PM

I have no "ProfileNotification, Windows 10

Thursday, March 14, 2019 3:13 PM | 2 votes

OK, first, you need to get a copy of SetACL from helgeklein. just google it.  its a tiny tool and incredibly useful. there is a 32bit version and a 64bit version. be sure to use the one that is correct for your OS. obviously...

Then, from an elevated cmd prompt, you use these commands (with SetACL.exe or SetACL64.exe respectively)

setacl -on "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileNotification" -ot reg -rec yes -actn setowner -ownr n:Administrators

setacl -on "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\ProfileNotification" -ot reg -rec yes -actn setowner -ownr n:Administrators

Next, use the reg command to delete the offending keys. Dont panic if you get an error saying they dont exist. 

REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileNotification\TDL" /v CLSID /f 

REG DELETE "HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\ProfileNotification\TDL" /v CLSID /f  

That should be all you need to do.  

I have to do this to a ton of computers, so I wrote a couple batch files to do it.  I have one called TakeOwnReg.bat which will take ownership of any reg key that I feed it from the command line, be it on localmachine or remote.  This is a really useful too all by itself. Just make sure the setacl files are in the path.   Then I have another one that I use to call the takeownreg script to take ownership of the offending keys, then purge them.  it can be used with \computername in the command line to tell it to fix a domain computer remotely. 

First, create a batch file called "takeownreg.bat" with this code:

@echo off &>nul 2>&1 fsutil dirty query %systemdrive% || echo CreateObject^("Shell.Application"^).ShellExecute "%~0", "%*", "", "runas", 1 > "%temp%\uac.vbs" && "%temp%\uac.vbs" && exit /b & CD /d %~dp0
setlocal EnableDelayedExpansion

echo.
echo Take ownership of the registry key specified on the command line or entered at the prompt.
echo requires setacl to be present in the path.
echo.
echo Syntax:
echo Takeownreg HKCR\Directory\
echo Takeownreg "HKCR\Keyname with spaces in quotes\"
echo.

if /i "%2"=="/q"( rem skip check option selected
set "choice=%1"
call :PROCESS
goto exit
)

if "%~1"=="" (echo No reg key selected... 
goto CHOICE)

rem set the choice variable to whatever was included on the command line
set "choice=%1"

echo.You have selected the registry key "%choice:"=%" 
goto check

:CHOICE
set /p choice=Please enter the desired registry key you would like to take ownership of. ^> 
if not defined choice (echo no Registry key selected. bailing out.
timeout 10
goto exit
)

:check 
echo Checking if reg key exists... 
reg query "%choice:"=%" /ve >nul 2>&1

IF ERRORLEVEL 1 (echo Reg key not found. try again
set choice=
goto CHOICE
)

:process
rem use 32 or 64bit setacl
If EXIST "C:\Program Files (x86)" (set setacl=setacl64.exe
) else (set setacl=setacl.exe)
echo.
echo processing.
%setacl% -on "%choice:"=%" -ot reg -rec yes -actn setowner -ownr n:Administrators
%setacl% -on "%choice:"=%" -ot reg -rec yes -actn ace -ace n:Administrators;p:full


IF ERRORLEVEL 1 (echo something went wrong...
) else echo registry permissions updated successfully. 
echo.
:exit

Next, create a second batch file called "fix eventid 1534 tiledatalayer.bat" with this code.

@echo off &>nul 2>&1 fsutil dirty query %systemdrive% || echo CreateObject^("Shell.Application"^).ShellExecute "%~0", "%*", "", "runas", 1 > "%temp%\uac.vbs" && "%temp%\uac.vbs" && exit /b & CD /d %~dp0
setlocal EnableDelayedExpansion

rem event id 1534 fix for TileDateLayer errors after updating to windows 10 1809

:Usage
rem Use "fix eventid 1534 tiledatalayer.bat" for localmachine, or append a computername to it to use on a remote machine

set Target=localhost
if NOT "%1"=="" (
 set TARGET=%1
 PING -n 1 -w 100 !TARGET:\=! >nul 
 if ERRORLEVEL 1 (echo !TARGET! not found. Exiting... 
  timeout 30
  goto EXIT
 )
set TARGET=\\!TARGET:\=!\HKEY_LOCAL_MACHINE
)
echo target is !TARGET!
if /i "!TARGET!" EQU "localhost" set TARGET=HKEY_LOCAL_MACHINE

call takeownreg.bat "!TARGET!\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileNotification" /Q
call takeownreg.bat "!TARGET!\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\ProfileNotification" /Q

REG QUERY "!TARGET!\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileNotification" /s /f {B31118B2-1F49-48E5-B6F5-BC21CAEC56FB}
REG QUERY "!TARGET!\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\ProfileNotification" /s /f {B31118B2-1F49-48E5-B6F5-BC21CAEC56FB}

echo.
echo Deleting offending keys...
REG DELETE "!TARGET!\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileNotification\TDL" /v CLSID /f 
REG DELETE "!TARGET!\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\ProfileNotification\TDL" /v CLSID /f  

timeout 30
:EXIT

then just run the command "fix eventid 1534 tiledatalayer.bat" for localmachine, or append a computername to it to use on a remote machine

if you want to get fancy, you could use dsquery to get a list of computers on your domain, and call the fix for each one, but thats for another post.  

Wednesday, March 20, 2019 1:59 PM

"Furthermore, Please log on as an administrator, launch regedit and change the ProfileImagePath value in the key that ends in ".bak" to match the actual profile folder name.  Alternatively, you can change the name of the profile to match the ProfileImagePath value in the key that ends in ".bak".  After you fix the mismatch, change the key name that does not have ".bak" in it by adding an extension such as ".old".  Then remove the ".bak" extension from the correct profile key.

In addition, check if your domain account belongs to Domain Guest group. If yes, remove it."

TOO COMPLICATED. MAKE STEP BY STEP VIDEO.

YES HELP ALOTE IN VIDEO,I CANOT TO DELETED THIS TDL.

Wednesday, March 20, 2019 2:00 PM

i need to guys...please help me.

Wednesday, March 20, 2019 2:01 PM

Hi

Would a registry cleaner such as ccleaner remove the unused registry keys?

no...c cleaner do nothing.

Wednesday, March 20, 2019 2:02 PM

yes ok,but the freeze stil happend.

Thursday, May 2, 2019 10:13 AM | 1 vote

On windows server 2016 (windows10) 

1. run CMD as administrator

2. type QWINSTA - to view logged users and sessions  ID

3. look for sessions of your profile (or other users who have problem) - your curent session is marked with ">"

4  LOGOFF  "ID" -  where ID is the number of the session (ID colon).  EXAMPLE: LOGOFF 77

5. Kill all sessions and try to login again with problematic user 

This work for me on server 2016 with RDS users.

Tuesday, May 7, 2019 6:05 PM

Can't have Administrators FC, had to add specific user FC.  Once used single user worked.

Thursday, May 16, 2019 8:22 PM

This worked for me. Now I do not see the event entries anymore!

Thanks for the solution JonnyPhenomenon!

Sunday, August 4, 2019 10:01 PM

How do you do this manually?

Jon A Martinez MCSE

Sunday, August 4, 2019 10:05 PM

I'm logged in as admin and both of these only show an entry called default and no TDL key. Should I delete default? Thanks

Jon A Martinez MCSE

Sunday, August 4, 2019 10:35 PM

Thanks the first file opened and closed in a fast black box, the second file gave me two access denied errors messages and closed out after 30 seconds. I was logged on as an admin. Reboot necessary?  Do I have to log in in safe mode as admin? I'm from windows 2000 pro not not win 10 pro. Thanks.

Jon A Martinez MCSE