Windows 10: What is the cause of Network Error Code 0xC00D426A and why hasn't it been fixed after Build...

Now Windows 10 consistently tries to get me to upgrade the desktop from build 1703 [15063.1418] to build 1909.


Finally sick of this pestering I allowed Windows to update my laptop to see if Microsoft have actually fixed the dreaded Network Error Code 0xC00D426A.


No they haven't, it still persists - why isn't it a problem in build 1703 - yet it is in every build since then? I can't even find detail on precisely what Network Error Code 0xC00D426A actually is or find a work around.


Google search will only direct you exclusively to my earlier complaints over the last few years.


Is there any real technical help anywhere - I gave up years back asking other questions/making suggestions on Windows Insiders as the Microsoft staff there regarded anyone NOT getting with the Microsoft program as an heretic and very likely a communist.


If you are into Flim/Flam/Features you will likely get an avid audience, if you have serious technical questions then go away somewhere else...

:)

 

Build 1803 still causing copy "Error Code 0xC00D426A: Error reading from the network"

Does anybody know for certain if Mr Microsoft has ever gotten around to fixing this annoying error in subsequent revisions and updates?

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

To copy over the LAN the easy way I have to use my Laptop with build 1703 - it works.

The hard way is to:

a) Persevere and it sometimes works properly OR;

b) Wait for the "Error Code 0xC00D426A" message then...

Open up C:\Users\ME\AppData\Yadda\Yadda where you will find the very same file without the proper file name, only some number assigned to it by File Explorer...

This is ridiculous and a known fault yet to be fixed by Microsoft, and people wonder why so many of us now refuse updates. Updates which not only do
NOT fix prior problems, but introduce whole new ones.

Oh and all my Windows versions over the great many years were "Retail - paid for up front versions for custom built desktops" not OEM.

Regds

Ian C. Purdie - Sydney

 

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

I had previously posted this very same identical problem on May 27, 2018.

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

I successfully followed that advice - problem solved.

Recently with another update [now to Build 1803] the problem has now reoccurred.

I updated today to the latest 1903 Build 18362.418

Problem still persists - identical replica to the one last May.

God I hate rotten updates - never anything except unwanted problems.

Thanks in advance

Ian

 

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

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