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(48, 12%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWL%3C/text%3E%3C/svg%3E)
Any one seen this issue ,only occurring in about the last week. It maybe a wider issues globally. Not sure what triggered it.
Basically in the last few days some updates from 1809 to 1909, after completed, the local laptop certs are missing. Which is a problem for all our home users on VPN! (i.e. with covid still around)
For all users who use the servicing in MEMCM: Yesterday Microsoft has updated the Servicing Image in WSUS. So the problem with the IPU via Servicing does not occur anymore. This applies to the images 1909, 2004, 20H2.
So, download the image again and deploy it! But I could not test it yet.
![](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(211.20000000000002, 27%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
Has Microsoft confirmed that this image contains the fix?
![](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(51.2, 86%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERL%3C/text%3E%3C/svg%3E)
we were already in the process of preparing 1700 devices to upgrade from 1809 to 1909 via SCCM task sequence.... the 1700 clients already downloaded the upgrade-image (dating from April 2020 because we started piloting the first devices around that time of the year) into their ccmcache folder and we disabled the actual upgrade task sequence once reading these internet-posts about certificates being lost.
We could refresh the installation image (which is used in the upgrade task sequence) to the latest one released by MS (version 2004, 20H2) but that would mean all 1700 clients need to download this newer image file (again 4,5 GBs to be downloaded).
Is there another smoother way to upgrade from 1809 to 1909? For example: does the cumulative update from November 2020 for 1809 contain the needed fix so the certificates don't get lost when upgrading from 1809 to 1909?
![](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(99.2, 92%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGA%3C/text%3E%3C/svg%3E)
hi guys, I was reading this post, I upgraded my first PC from 1809 to 1909 com sccm a week ago in test environment. I don't have any problems. what should i check ??? thanks for the replies.
![](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(137.6, 87%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECL%3C/text%3E%3C/svg%3E)
Check you certificate Store with the mmc.
System and user certificates might be lost when updating a device from Windows 10, version 1809 or later to a later version of Windows 10. Devices will only be impacted if they have already installed any Latest cumulative update (LCU) released September 16, 2020 or later and then proceed to update to a later version of Windows 10 from media or an installation source which does not have an LCU released October 13, 2020 or later integrated. This primarily happens when managed devices are updated using outdated bundles or media through an update management tool such as Windows Server Update Services (WSUS) or Microsoft Endpoint Configuration Manager. This might also happen when using outdated physical media or ISO images that do not have the latest updates integrated.
![](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(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
We had a case opened at Microsoft for this issue and they confirmed that it has been adressed with the new release of the Feature Update Packages in the SCCM Servicing Node on November 11. I see that the Feature updates in my existing deployment are superseded and new ones are available now.
Now we have deployed the new Feature Update Package to a test device and it did not loose the Certificates after the update. So the issue seems to be fixed for the case of SCCM-Servicing Update.
For all other cases, I cannot tell you if the November Cumulative Update for 1809 has fixed the issue for the case where one deploys an outdated 1909 Image for example with a task sequence to an up-to-date 1809 client.
I have tested the Feature Upgrade from 1809 to 1909 with new image on two computers for now in our environment.
Both still have their certificates left - seems to be working/fixed.
Will update here, as soon as I got a few more tests done.