says '19042.661' and has the link to the (now non-existent) Insider. In fact an example of how mixed up the threads got is that the link you quoted from Brink. Not one of Microsoft's finest hours.Īs a consequence the threads here got messy too, and the 645 posts of what is now titled KB4586853 CU Windows 10 v2004 build 19041.662 and v20H2 19042.662 were originally three separate threads, Insider. 662 - they had to restore a 19042.630 image or do a repair install. 661 to find that they then couldn't update from. It all got very messy and had to be replaced with the Insider release of 19042.662 - only for those on. It was an Insider preview build that had to be re-released about four time to fix other bugs it introduced. Yes, 19042.661 did fix the issue - but at a cost. I have run 20H2 since 20th October's release and have followed its every twist and turn, starting with testing the registry hacks to allow apps and files to be kept in a repair install. I understand that you don't run 20H2 yet so you probably haven't been involved in the full horrors that went on in the month of November. You would have seen that was so had you clicked on the link.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |