bwolken

Join Date 11/2012

Metro Apps Broken

Only when Decor8 Installed

Just reporting an issue that I've confirmed on several PCs running several different hardware configurations. I installed Decor8 on each of these PCs. While things seemed to be running fine, I noticed that over time, metro apps stopped working. Eventually, I couldn't even load the store. After uninstalling Decor8, all metro apps load like normal and continue to run fine for days (have not tested beyond 3-4 days).

decor8

Locked Post

Advanced Search

Watch this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

Did you reboot any of the machines after the problem to see if it continued?

Successfully updated karma reason!

Yes. Prior to uninstalling Decor8, I rebooted each of them several times to no avail. On all of the machines I tested, as soon as Decor8 was removed, all of the metro apps continued working as normal. What I found particularly odd is that aside from the built in metro apps, apps like Netflix, etc. also stopped working with Decor8 installed.

Successfully updated karma reason!

Having the same exact issue. Store stopped working along with all metro apps. Think it was after I changed the lock screen.

Successfully updated karma reason!

Could we have some more information please.

1) Could you check taskmanager and see how much memory is in use overall and in use by explorer (see details tab)

2) Does the issue continue instantly after you reboot your machine, or does it take time to happen again?

3) If it is instant, could you run services.msc, find Stardock Decor8 and set it to manual and reboot again and see if everything has returned to normal

4) If that did help, set it back to automatic, reboot and then try setting a different background, then reboot again and see if the problem continues.

Also are you using a custom colour scheme, auto created from the background, or standard one?

Successfully updated karma reason!

1) 0.4 MB

2) Yes, it is persistent.

3) It did not. It's odd ... the only thing I did before store stopped working was change by lockscreen and now that seems to be a persistent issue. It says I need to refresh windows to fix it.

4) N/A

5) I use the auto creation.

Successfully updated karma reason!

Do you have another user account on the machine. I would be curious to know if that works ok.

From the sounds of it something in your user account has corrupted itself. That shouldn't be caused by Decor8 as we do not do anything with that with the exception of the lock screen changing, but we simply ask the OS to use a new image via the provided apis. It is possible there is an OS level issue with that which can cause some sort of corruption of course.

Did you rapidly change lock screens and had you previously changed lock screens ok?

Successfully updated karma reason!

I tried another user and same deal.

I changed my lock screen often while finding one I liked.

I did a sfc /scannow as admin in powershell and saw a lot about img100.png in there:

2012-12-13 06:27:09, Info                  CSI    000006c2 [SR] Beginning Verify and Repair transaction

2012-12-13 06:27:09, Info                  CSI    000006c3 [SR] Verify complete

2012-12-13 06:27:09, Info                  CSI    000006c4 [SR] Repairing 1 components

2012-12-13 06:27:09, Info                  CSI    000006c5 [SR] Beginning Verify and Repair transaction

2012-12-13 06:27:09, Info                  CSI    000006c6 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-themeui-client_31bf3856ad364e35_6.2.9200.16384_none_c60cdb25defbc594\img100.png do not match actual file [l:20{10}]"img100.png" :

Found: {l:32 b:ZvCpsup3yQreFvfjLMMfy9mWJK3h9GxpS5Hp+M+U6JQ=} Expected: {l:32 b:uY9CPvRWct/Qjjbx7SJ5uKSnx5ejSjNJUHv25oqV64w=}

2012-12-13 06:27:09, Info                  CSI    000006c7 [SR] Cannot repair member file [l:20{10}]"img100.png" of Microsoft-Windows-ThemeUI-Client, Version = 6.2.9200.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2012-12-13 06:27:09, Info                  CSI    000006c8 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-themeui-client_31bf3856ad364e35_6.2.9200.16384_none_c60cdb25defbc594\img100.png do not match actual file [l:20{10}]"img100.png" :

Found: {l:32 b:ZvCpsup3yQreFvfjLMMfy9mWJK3h9GxpS5Hp+M+U6JQ=} Expected: {l:32 b:uY9CPvRWct/Qjjbx7SJ5uKSnx5ejSjNJUHv25oqV64w=}

2012-12-13 06:27:09, Info                  CSI    000006c9 [SR] Cannot repair member file [l:20{10}]"img100.png" of Microsoft-Windows-ThemeUI-Client, Version = 6.2.9200.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

2012-12-13 06:27:09, Info                  CSI    000006ca [SR] This component was referenced by [l:268{134}]"Microsoft-Windows-Client-Features-Package-shell~31bf3856ad364e35~amd64~~6.2.9200.16384.Microsoft-Windows-Client-Features-Package-shell"

2012-12-13 06:27:09, Info                  CSI    000006cb Hashes for file member \??\C:\Windows\Web\Screen\img100.png do not match actual file [l:20{10}]"img100.png" :

Found: {l:32 b:ZvCpsup3yQreFvfjLMMfy9mWJK3h9GxpS5Hp+M+U6JQ=} Expected: {l:32 b:uY9CPvRWct/Qjjbx7SJ5uKSnx5ejSjNJUHv25oqV64w=}

2012-12-13 06:27:09, Info                  CSI    000006cc Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-themeui-client_31bf3856ad364e35_6.2.9200.16384_none_c60cdb25defbc594\img100.png do not match actual file [l:20{10}]"img100.png" :

Found: {l:32 b:ZvCpsup3yQreFvfjLMMfy9mWJK3h9GxpS5Hp+M+U6JQ=} Expected: {l:32 b:uY9CPvRWct/Qjjbx7SJ5uKSnx5ejSjNJUHv25oqV64w=}

2012-12-13 06:27:09, Info                  CSI    000006cd [SR] Could not reproject corrupted file [ml:520{260},l:50{25}]"\??\C:\Windows\Web\Screen"\[l:20{10}]"img100.png"; source file in store is also corrupted

2012-12-13 06:27:09, Info                  CSI    000006ce [SR] Repair complete

2012-12-13 06:27:09, Info                  CSI    000006cf [SR] Committing transaction

2012-12-13 06:27:09, Info                  CSI    000006d0 Creating NT transaction (seq 2), objectname [6]"(null)"

2012-12-13 06:27:09, Info                  CSI    000006d1 Created NT transaction (seq 2) result 0x00000000, handle @0xdc4

2012-12-13 06:27:09, Info                  CSI    000006d2@2012/12/13:11:27:09.875 Beginning NT transaction commit...

2012-12-13 06:27:09, Info                  CSI    000006d3@2012/12/13:11:27:09.875 CSI perf trace:

CSIPERF:TXCOMMIT;5920

2012-12-13 06:27:09, Info                  CSI    000006d4 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

Successfully updated karma reason!

Any update on this? It's not a big issue for me, because I don't use windows8 store for anything ... but it may be something worth fixing for others.

Successfully updated karma reason!

I have the same issue. I also don't use Windows 8 apps, so no big deal to me.

Successfully updated karma reason!

Agreed. An update would be great. This is a real deal breaker for me - unfortunately I do browse the windows 8 store from time to time.

Successfully updated karma reason!

Is there anything in the eventlog?

Successfully updated karma reason!

Oh, ffs ... ok, here is the fix which I tried myself once I finally found where Win8 actually kept the damn eventlogs (Worse navigation then even itunes) ...

1. Find the \ProgramData\Microsoft\Windows\AppRepository\ directory

2. Take ownership of it.

3. Delete all contents of the directory.

4. Launch your metro app.

Should work fine after that. I have no idea why it became corrupted as the only thing I installed before it went haywire was Decor8, Start8, and Fences2.

Admin Events:

1. msiexec (9160) Instance: The log range read from the file "C:\ProgramData\Microsoft\Windows\AppRepository\edb.log" at offset 12288 (0x0000000000003000) for 4096 (0x00001000) bytes failed verification due to a range checksum mismatch. The expected checksum was 8589934704 (0x200000070) and the actual checksum was 9807191426 (0x2488ddd82). The read operation will fail with error -501 (0xfffffe0b). If this condition persists then please restore the logfile from a previous backup.

2. msiexec (9160) Instance: Corruption was detected during soft recovery in logfile C:\ProgramData\Microsoft\Windows\AppRepository\edb.log. The failing checksum record is located at position END. Data not matching the log-file fill pattern first appeared in sector 3 (0x00000003). This logfile has been damaged and is unusable.

3. msiexec (9160) Instance: The log range read from the file "C:\ProgramData\Microsoft\Windows\AppRepository\edb.log" at offset 12288 (0x0000000000003000) for 4096 (0x00001000) bytes failed verification due to a range checksum mismatch. The expected checksum was 8589934704 (0x200000070) and the actual checksum was 9807191426 (0x2488ddd82). The read operation will fail with error -501 (0xfffffe0b). If this condition persists then please restore the logfile from a previous backup.

4. msiexec (9160) Instance: Corruption was detected during soft recovery in logfile C:\ProgramData\Microsoft\Windows\AppRepository\edb.log. The failing checksum record is located at position END. Data not matching the log-file fill pattern first appeared in sector 3 (0x00000003). This logfile has been damaged and is unusable.

5. msiexec (9160) Instance: The log range read from the file "C:\ProgramData\Microsoft\Windows\AppRepository\edb.log" at offset 12288 (0x0000000000003000) for 4096 (0x00001000) bytes failed verification due to a range checksum mismatch. The expected checksum was 8589934704 (0x200000070) and the actual checksum was 9807191426 (0x2488ddd82). The read operation will fail with error -501 (0xfffffe0b). If this condition persists then please restore the logfile from a previous backup.

6. msiexec (9160) Instance: Corruption was detected during soft recovery in logfile C:\ProgramData\Microsoft\Windows\AppRepository\edb.log. The failing checksum record is located at position END. Data not matching the log-file fill pattern first appeared in sector 3 (0x00000003). This logfile has been damaged and is unusable.

7. msiexec (9160) Instance: Database recovery/restore failed with unexpected error -501.

Successfully updated karma reason!

Hi!

I had that issue long before Decor8. If you Google it, you'll see lots of people have that issue, and there are many tips on how to resolve it. (None of them worked for me though, I did a fresh install of Windows 8 and now that has worked for a week - with Decor8). Touch wood

Brgds

Danny

Successfully updated karma reason!