This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 48%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJH%3C/text%3E%3C/svg%3E)
Have attempted to upload builds from Azure DevOps as well as local, both fail to upload with the above error.
Package can be installed locally however, and the packages passes all tests in the App Certification Kit.
Any ideas what the issue might be?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 53%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENS%3C/text%3E%3C/svg%3E)
I'm seeing the same problem trying to do a new submission on an existing application.
Retrieving the COM class factory for component with CLSID {378E0446-5384-43B7-8877-E7DBDD883446} failed due to the following error: 800b0101 A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. (Exception from HRESULT: 0x800B0101)
My system clock looks good when I compare to time.gov. Wonder if this is a Store issue?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(272, 94%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESW%3C/text%3E%3C/svg%3E)
It seems there is something going on with the Store. I am receiving this error as well. I uploaded a different version less than a week ago. There is another thread on this site with people having the same problem.
Edit: Link to other thread: https://learn.microsoft.com/en-us/answers/questions/64364/upload-uwp-app-to-microsoft-store-has-validation-e.html
Do you have a link to that? I couldn't find anything related when I originally posted.
Found it, and posted there too.
It was a bit late, but I went ahead and added a link to my original comment in case anyone else is looking.
My upload finally went through. I didn't do anything special. I deleted the failed package and re-uploaded the exact same .appxupload file.
Either I got lucky, or the underlying issue was corrected.
I'm getting
"Package acceptance validation error: The package file format for (AppBunbleName).appxbundle is invalid: Retrieving the COM class factory for component with CLSID {(app's guid)} failed due to the following error: 800b0101 A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. (Exception from HRESULT: 0x800B0101).. Update the package and try again."
with an app that worked fine submitting yesterday.
We have a major release that has been over 1 year in the making scheduled for release today.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(233.6, 43%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPK%3C/text%3E%3C/svg%3E)
Same here The package file format for Deployer_4.0.4.0_x64.msixbundle is invalid: Retrieving the COM class factory for component with CLSID {378E0446-5384-43B7-8877-E7DBDD883446} failed due to the following error: 800b0101 A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file. (Exception from HRESULT: 0x800B0101).. Update the package and try again.
Package submissions seemed to start working again correctly after 12PM PST, 11th of August 2020. Also the package was created with Visual Studio 16.7.1 which released this morning, but not sure if that made a difference. Seems to be hit and miss though, keep trying.
Look for the GREATLY improved Notebook Pro 2.4 later today!!
Success! I had to create a new package this evening to replace the one created this morning which continues to fail validation. This allowed me to move the submission into certification.