luminar4.3 hangs at splash screen after Update
Answered
Hello,
after deleting the app, i renamed the Appdata folder to .old , as stated earlier, and run the Setup as Administrator.
Then it said, the Evaluation Period expired. So i used another of my Liceses.
Luminar started in Version 4.3 and i had tu build a new Cathaloge. Everything was looking quite normal, until i quit the Program. Trying to start one again, i had the same trouble as before. It hangs at splash screen, no matter if run it as Admin or normal.
This is very very very annoying
regards
-
Official comment
Hi Michael, please accept our sincere apologies for the problems you’ve been facing with the last update. We're currently investigating this issue and hope to be able to provide a definite solution soon.
It would help us a lot if you could provide us with event logs.
To collect them,
- Reproduce the issue.
- Press the Windows logo key + R.
- Type eventvwr in the dialog box that opens and hit Enter on your keyboard.
- In the window that opens click the triangle next to Windows Logs on the left. A directory tree should open.
- Click Application in the directory tree.
- In the main part of the window find the two topmost entries marked with Error named Application Error and .NET Runtime.
- Hold CTRL and click your left mouse button on each entry to select them both.
- Right-click on any of the two selected entries and click Save Selected Events.
- Name the file, save it, and attach it to your support request at skylum.com/support
Besides, please send us logs from the following folder too:
Press the Windows logo key + R.
Type %appdata%\Luminar 4\mipl\Logs in the dialog box that opens and press Enter on your keyboard.
Thank you in advance!Comment actions -
This happened on one of my machines, but not the other (for whatever reason).
I could not find ANY errors in the Event Viewer for 'Application Error' or '.NET Runtime'. However, I DID find a number for ESENT (svchost (18664,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log.).
So I Googled for TILEREPOSITORYS-1-5-18: Error -1023, and found https://www.youtube.com/watch?v=DgkjYW09ng0.
in short, you create a new folder tree TileDataLayer\Database in C:\Windows\System32\config\systemprofile\AppData\Local (if it doesn't already exist).
That's all - Luminar4.3 now works - not even a re-boot required.
Good luck!
-
The first thing I found is that deleting the contents of C:\Windows\System32\config\systemprofile\AppData\Local\TileDataLayer\Database gets Luminar4.3 starting again. And looking at the time stamps, these files appear to have been put there by Luminar4.3.
But there were NO errors in the Event log this time.
And the other piece of bad news is that on my other machine (where it starts every time) there is NO TileDataLayer\Database. And also no errors in the Event Viewer (but I didn't expect any).
Yet it starts.
Versions of Windows are the same, but radically different hardware (Core i7 vs Core i9, nVidia GTX1050 vs RTX2080, etc).
Given that quite a few seem to be suffering from this, I am a bit surprised that the software got out of QA.
Nigel
-
Thanks. But I'm done.
Skylum has to do its homework. I'ts not our task, to debug false updates :(
Btw., Skylum works hard, to annoy the rest of her optimistic costumers.
After 4 years I will no longer trust in Skylums skills to deliver the bunch of over years promised features. Neither I trust Skylum to provide working updates.
EM
-
mmm, I noticed a thing... maybe it's a useless clue...
Is it possible that TileDataLayer is something related to the windows start menu tiles?
I had Luminar pinned in a tile. Maybe that's the reason of the bug?Also, as stated here https://community.spiceworks.com/topic/2136456-where-is-windows-10-tile-database-located-in-2018 TileDataLayer is deprecated in favour of TileStore.
Maybe Luminar is using somewhere that feature removed since win build 1709?
Please sign in to leave a comment.
Comments
12 comments