Troubleshooting New MS Store App Install Error 0x00000000

Published On: January 12, 2023Last Updated: January 11, 2024By Tags: 2.2 min readViews: 91

TOC

While performing some work out in the wild, it was noted that one of the Microsoft Store Apps (New) would not install unless excluded from all policies. The app in this case was the Company Portal app which is pretty vital for self-service application delivery. The error displayed was
0x00000000 in the Intune console as below.

intuneStates
intuneStates

So I put down my configuration hat and brushed off the dust on the troubleshooting hat and got it nicely placed on my noggin and got stuck in.


Finding the Problem

As with all troubleshooting the first step is Logs, so lets open up C:ProgramDataMicrosoftIntuneManagementExtensionLogsIntuneManagementExtension.log. I did troubleshooting using Notepad… if your going to troubleshoot, you need to do it hardcore right? But you can open it in any editor or CMTrace etc.

Once launched, if you search for WinGet and you will be able to locate the events that relate to the ‘New’ Store App deployments via Intune.

Looking through the logs I came across the lovely gem below;

blockedByPolicy
blockedByPolicy

This was somewhat of a relief to see, as it had actual error information, rather than just the 0x00000000 error code.

Following on from finding this, I opened up PowerShell as the user and tried to install the app manually for additional validation and I got the below;

wingetFailed
wingetFailed

 

Taking a quick look at the configuration applied to the machine, I noted that there was an ADMX backed policy that Turned Off the Microsoft Store.

turnOffStore
turnOffStore

 

I didn’t want to go through the hassle of changing the policy off the bat, I wanted to validate my thinking. I located the policy it controls in the registry under the HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsStore Key. Thd value I was looking for was RemoveWindowsStore. When located as shown below the value was set to 1.

regeditPolicyKey
regeditPolicyKey

A quick change to set it to 0, and then back over to PowerShell to try it out again. An low and behold, it works first time.

wingetSuccess
wingetSuccess

This is then identified by Intune as installed, even after reverting the registry key back to 1.

gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==
gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==

 

Conclusion

I am by no means suggesting this is the only thing that causes the 0x00000000 error code, It has also been noted that it can be caused by Insufficient Connectivity to the store, which in the case I’ve seen it looks to be caused by proxy/network configuration. I am sure this will not be the last of the phantom errors either, so please comment below if you come across this in any other scenario to help keep this post updated.

I hope you find this useful and it solves your problem.

Troubleshooting New MS Store App Install Error 0x00000000

Published On: January 12, 2023Last Updated: January 11, 2024By Tags: 2.2 min readViews: 91

TOC

While performing some work out in the wild, it was noted that one of the Microsoft Store Apps (New) would not install unless excluded from all policies. The app in this case was the Company Portal app which is pretty vital for self-service application delivery. The error displayed was
0x00000000 in the Intune console as below.

intuneStates
intuneStates

So I put down my configuration hat and brushed off the dust on the troubleshooting hat and got it nicely placed on my noggin and got stuck in.


Finding the Problem

As with all troubleshooting the first step is Logs, so lets open up C:ProgramDataMicrosoftIntuneManagementExtensionLogsIntuneManagementExtension.log. I did troubleshooting using Notepad… if your going to troubleshoot, you need to do it hardcore right? But you can open it in any editor or CMTrace etc.

Once launched, if you search for WinGet and you will be able to locate the events that relate to the ‘New’ Store App deployments via Intune.

Looking through the logs I came across the lovely gem below;

blockedByPolicy
blockedByPolicy

This was somewhat of a relief to see, as it had actual error information, rather than just the 0x00000000 error code.

Following on from finding this, I opened up PowerShell as the user and tried to install the app manually for additional validation and I got the below;

wingetFailed
wingetFailed

 

Taking a quick look at the configuration applied to the machine, I noted that there was an ADMX backed policy that Turned Off the Microsoft Store.

turnOffStore
turnOffStore

 

I didn’t want to go through the hassle of changing the policy off the bat, I wanted to validate my thinking. I located the policy it controls in the registry under the HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsStore Key. Thd value I was looking for was RemoveWindowsStore. When located as shown below the value was set to 1.

regeditPolicyKey
regeditPolicyKey

A quick change to set it to 0, and then back over to PowerShell to try it out again. An low and behold, it works first time.

wingetSuccess
wingetSuccess

This is then identified by Intune as installed, even after reverting the registry key back to 1.

gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==
gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw==

 

Conclusion

I am by no means suggesting this is the only thing that causes the 0x00000000 error code, It has also been noted that it can be caused by Insufficient Connectivity to the store, which in the case I’ve seen it looks to be caused by proxy/network configuration. I am sure this will not be the last of the phantom errors either, so please comment below if you come across this in any other scenario to help keep this post updated.

I hope you find this useful and it solves your problem.