Hi Joseph,
I would like to say thank you for coming back on this. I'm afraid that what you have suggested hasn't worked and the issue which is caused by the upgrade to the Fall Creators Update still exists.
I can confirm that when I performed the operations with the SFC and DISM tool last week, I booted the machine in the 'Clean Boot' state, as this is part of what I do prior to running the tools. So this didn't work.
I will be running another SFC and DISM utilities in a Clean Boot state following the installation of the new Cumulative Update that Microsoft is scheduled to be released on the 14th of November (Patch Tuesday). I will most likely install this on the weekend
of the 17th, 18th and 19th of November - as I'm travelling during the week and staying in a hotel with a captive and capped wifi network. So I will need to wait until I get home with a faster network.
I am unable to roll back to the previous Build of Windows 10 - the Creators Update, as I got rid of the Previous Version of Windows, using the Disk Clean Up utility. I did this before realising that the File History component is ignoring the local OneDrive
replicas. Therefore this is not possible.
I can confirm that I logged a piece of Feedback last week prior to commenting on this thread and I stated this and included the URL for it. For completeness, it is here - https://aka.ms/C4vg1h
I am not prepared to perform a Restore of the system at this time, as all else is working fine and you've not currently provided sufficient support or ideas to justify this course of action.
This piece of feedback has been up voted twice in the last week. So this issue is appearing to be across a number of people's machines. I see that five people are watching this thread and two are watching my Feedback. Therefore this is becoming a wide
spread issue.
Can I ask - Are you a Microsoft employee? Your badge says that you are. Can I ask you escalate this with your contacts at Microsoft?
I have seen at this time, there isn't any available CUs at this following URL;
https://support.microsoft.com/en-us/help/4043454
With the above in mind. Can I please ask for you for your next suggestions and updates within Microsoft to get this resolved?
As I keep saying, all was well within the Creators Update - this issue has only started following the upgrade to the Fall Creators Update.
Many thanks in advance,
Kind regards,
Neil