Metro Apps All Crash On Startup - I have read the other threads on this

Question

UPDATE: I AM UPDATING THIS FIRST POST AS PEOPLE KEEP INCORRECTLY MARKING OUR ISSUE AS ANSWERED WHEN THEY HAVE NOT READ THE THREAD PROPERLY. AS SUCH I WILL START BY SAYING IF YOU ARE COMING HERE AND USING AVAST THEN YOUR SOLUTION WILL BE TO TURN OF THE BEHAVIOR SHIELD
FUNCTION. MORE INFO IS CONTAINED ELSEWHERE ONLINE ON THIS MATTER. THIS THREAD IS ABOUT DOMAIN USE OF METRO ON CLEAN INSTALLS WITH NO 3RD PARTY SOFTWARE. SORRY FOR THE CAPITALS BUT 5 TIMES HAVE PEOPLE MARKED AVAST AS THE ANSWER TO OUR PROBLEM WHEN IT IS NOT
EVEN INSTALLED AS DESCRIBED IN THE THREAD. I HAVE POSTED AN EXACT STEP BY STEP TO REPRODUCE MY PROBLEM LOWER DOWN
I know this question has been asked several times but there seems to be no-one that has a fix for it and it's becoming very frustrating.
I have installed windows 8 on my work computer as part of a test group to evaluate how the OS runs in our corporate space. The answer currently is not very well. The desktop side runs lovely but the whole metro experience is currently broken. This is the
same across all the people in our test group, not just my machine.
Scenario:
All users running windows 8 within our domain are unable to launch any metro (sorry - new style) application with the exception of PC settings.
I will describe how I set my machine up and the errors I receive.
The install is Windows 8 Pro that was a totally clean install. Installation went fine and very fast which was great. When required during setup I created a local Microsoft account - we wanted to see the experience for the majority of users who
do not have a live id. This all worked fine and everything worked as expected - including the metro apps.
Now that everything was up and working we joined the machine to the domain, this went fine and I was asked what local security level I would like the account to have - I selected administrator as I need to install all my software / dev tools etc.
After reboot I log into my domain account and start to install all my applications. I didn't retest metro apps at this point as it never crossed my mind that I would need to.
All normal desktop apps / programs installed I try to show a colleague the news metro app. The splash screen flashes up and bang straight back to the start screen. I proceeded to try every single other metro app and all have the same result, including
the store. Strangely they are all displaying notifications and updating the tiles.
So now I start to search the issue online looking at my event logs for clues to track it down. The following is what i find in the event viewer, I will use the store as an example:
Under "Windows Logs" --> "Application" : I get two separate error events the first reads "Activation of app winstore_cw5n1h2txyewy!Windows.Store failed with error: The app didn't start. See the Microsoft-Windows-TWinUI/Operational log for additional
information." The second arrives in the log about 15 seconds after the first and reads "App winstore_cw5n1h2txyewy!Windows.Store did not launch within its allotted time."
Under "Windows Logs" --> "System" : I get one error that reads "The server Windows.Store did not register with DCOM within the required timeout."
Under "Applications And Services Logs" --> "Microsoft" -->  "Windows" --> "Apps" --> "Microsoft-Windows-TWinUI/Operational" : I get one error that reads "Activation of the app winstore_cw5n1h2txyewy!Windows.Store for
the Windows.Launch contract failed with error: The app didn't start."
I have tried the following to resolve this with no success:
Updated the registry as per a moderator suggestion on technet
Linked my domain account to my live id account
Tried changing permissions on C drive to allow all application packages full control
Install all latest updates
Tried to run from the local none domain account - same issue now occurs there
I am not willing to do a repair or re install after spending the best part of a day installing my programs and arranging my start menu too my desired layout. Also each user in our test group has the same issue with totally different software installed. The
only common item between the 5 systems is .net 3.5 has been installed in order to run a piece of custom software (a simple exe).
I need to try to find another spare machine to test if simply joining the domain is the root cause. If so this will surely be a big issue when it is actually release later this month as we do nothing special here in terms of our domain config. If it is something
to do with the domain Microsoft should be much more specific about what can and cant be done on the group policies if you want metro to run. There is no way we could roll this out to our users if as soon as they join our domain their entire start
screen stops working.
HELP!!!

Answer 1

Kevinio04, 
We have been experiencing the same error in our environment; however today I have found a solution for this.  I have included my theory too, as to why this was happening.  Let me know if this solution works for you:
If you have recently installed Windows 8 Enterprise on a machine, put the machine on a domain and then used Active Directory credentials to log in, then you may have
experienced all Metro Apps to crash.
Theory for Metro apps crashing: Once the machine was put on the domain and an Active Directory user would log into the Windows 8 machine group policy kicked in (depending on what OU that machine was in).  Group policy writes to the Windows registry;
therefore if you put that same machine in a different OU after previously being in a different OU, there are still traces of the previous group policy in the Windows registry.  In summary, a new OU needs to be created in group policy specifically for
Windows 8 machines.  The machines that are going to have Windows 8 installed on them, must start with a clean Windows 8 install. You can find details in the outline below:
GROUP POLICY CHANGES
Create a new Windows 8 OU with no policies enforced
Once that OU is created, create the following Policy:
Location of Policy: Computer Configuration / Policies / Windows Settings / Security Settings / Local Policies/Security Options / Audit: Audit the access of global system objects
This policy needs to be set to: Not Configured
Audit: Audit the access of global system objects
Default: Disabled
Description of this Policy
*This security setting determines whether to audit the access of global system objects. If this policy is enabled, it causes system objects, such as mutexes, events, semaphores and DOS devices, to be created with a default system access control list (SACL).
Only named objects are given a SACL; SACLs are not given to objects without names. If the Audit object access audit policy is also enabled, access to these system objects is audited.*
  INSTALL WINDOWS 8 ENTERPRISE
Administer a clean install of Windows 8 on a machine
Create a local administrator account
Log in with the location admin account to put the machine on the domain
Do NOT log onto the machine with Active Directory credentials yet!
Put the machine in the new Windows 8 OU
Restart the machine
Now, log onto the machine with Active Directory credentials
   TADA!