Error Code 0xC00D426A again: How to remedy and why it doesn't pay to update Windows 10

I

IanPurdie

Way back in May, 2018 when I upgraded to 1803 this intolerable problem emerged - ""Error Code 0xC00D426A: " so I was forced to go back to a stable [functional] build 1703. Here is that saga:


Build 1803 causing copy "Error Code 0xC00D426A: Error reading from the network %0 over LAN"

Build 1803 causing copy "Error Code 0xC00D426A: Error reading from the network %0 over LAN"


Since then over two years ago I have carried on more or less quite happily, whilst avoiding updates on every occasion.


Recently I have upgraded both Motherboard and CPU. So I cloned my SSD "C drive" to an old HDD and downloaded the latest Windows 10 upgrade - Ver 2004 Build 19041.450 - once installed I then enthusiastically copied over another file via my LAN to the HDD.


Initially it was looking real good... UNTIL...


Once again the dreaded ERROR 0XC00D426A struck again once more - Microsoft haven't even addressed this error.


Now I will put this into some perspective for many - my Desktop is a tool, nothing else. Consider this my parable.

"I have a tool which digs round holes. It is very good and efficient cutting down my time spent on holes.


Then the "HoleDiggerCompany" come along and tell me all about the most wonderful features of their latest hole digging machine. So I invest in that upgrade.


Once delivered I try it out - it digs perfect square holes, it digs perfect rectangular holes, it digs perfect oval holes, it can do everything except...


Dig Round Holes"



Another curious, and wasteful feature when their are no errors encountered in build 1703. File Explorer insist upon placing a copy of these files in:


C:\Users\MyName\AppData\Local\Microsoft... All of them with the file extension .dat - After a heap of Gigabyte files?


I have to go and clean out the folder C:\Users\My Name\AppData\Local\Microsoft... to conserve SSD space. No, the usual "CleanUps" don't do it.


Why can't Mr. Microsoft fix ERROR 0XC00D426A? I gave up on Windows Insiders because no Microsoft personnel there showed any interest beyond seeking adulation for Windows 10 - they would love Rudy Park.


[EDIT] Typo

Continue reading...
 
Back
Top Bottom