SOLVED Piloting client still old version after 1906 upgrade

[kvncrr]

This past weekend I upgraded from 1902 to 1906, then applied hotfix KB4517869. In Pre-Production Client Deployment under Monitoring, all clients show Failed or Not Compliant. Client version there shows 5.00.8853.1020, but when I look at details for ccmsetup.exe at C:\Program Files\Microsoft Configuration Manager\PilotingUpgrade, product version says 5.00.8853.1000. It appears the client from the 1906 upgrade remained after I applied the hotfix. Any idea how to get the right version of the client into the PilotingUpgrade folder so I can be deployed to my test group? I've tried Googling for the answer but have come up dry. Your help is much appreciated!

 

[kvncrr]

It occurred to me that I still have my VM snapshots from before the upgrade. Any harm in reverting now, and run the upgrade again going straight to 1906 KB4517869 rather than stepping to 1906 then the hotfix like I did before?

 

[Garth]

Yes, this will cause a ton of problems if you revet you VM.

 

[kvncrr]

I've got this in ccmsetup.log on a client

<![LOG[Retrieved package version '16'. But it is smaller than the expected version '17'. Content is not ready yet.]LOG]!><time="11:39:02.097+240" date="10-31-2019" component="ccmsetup" context="" type="2" thread="6024" file="siteinfo.cpp:351">

 

[kvncrr]

So the solution was to reboot the site servers. After everything came back up, clients in my pre-prod collection started showing upgrade successful and in progress.