Forum Moderators: open

Message Too Old, No Replies

Can't stop Feature Update annoying me.

Why?

         

IanCP

4:54 am on Dec 19, 2020 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



All through this week, every time I walk away from the desktop I come back to be greeted by:

RESTART - IMPORTANT FEATURE UPDATE [Paraphrasing]

Not Security Updates, just rubbish updates to stuff I will never use and couldn't care less about - but no fix to the dreaded Error, Build 1803 causing copy "Error Code 0xC00D426A.

This is an update to Windows 1909. Now I have in place all procedures to stop updates. Double checking now for the umpteenth time "Update and Security" , Advanced Options - - Feature Update can be deferred ... Deferred set 365 days.

Additionally on start up I run under CMD as Admin "net stop wuauserv"

Windows Update service is stopping
Windows Update service was stopped successfully

And I still get this rotten update business - now I waste time deleting:

a) $WINDOWS.~BT and the entire Windows folder...
b) SoftwareDistribution

Frigging weird.

Build 1803 causing copy "Error Code 0xC00D426A: Error reading from the network %0 over LAN"
[answers.microsoft.com ]

[Edit] - Add link

engine

4:55 pm on Dec 21, 2020 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



That sounds to me as if you're stuck in the middle between a couple of updates, and something has corrupted causing it to keep trying.
You have my sympathy.

I had one of those, and i've lost track. I gave up and went through the update, which took several reboots, and an age of my time. It was a nightmare, but I was getting so frustrated I let it do its thing. it finally shut up after about a week of various re-boots and new updated being applied. I finally got to a version that's stopped messing me around.
I dread patch Tuesday.

IanCP

11:51 pm on Dec 22, 2020 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Yes I took a couple of remedy actions - at least one has worked.

Anyway I'm going to roll out the laptop and let that update go ahead to see if that dreaded copy Error Code 0xC00D426A has been fixed.

If not I'll just roll back the update - much easier to do on the laptop.

[Typo]

tangor

12:46 am on Dec 23, 2020 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Chuckles ... I know what you mean about "... just rubbish updates to stuff I will never use and couldn't care less about..."

HOWEVER, there is nothing "rubbish" about what Win10 wants. Take it all as it comes (address what you want AFTER) or find errors creep in and eventually bork the critter. Been there, done that!

Good luck!

IanCP

7:39 pm on Dec 23, 2020 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Yes well after a painfully slow download - with updates - I finally late at night got the laptop up to Windows 1909.

As with all major updates the first thing I did was rename the file Windows.old to Windows.old.bak - that way I can revert back anytime of my own choosing.

Next I fired up Q-Dir to do a test file transfer over the Network. I selected a small 1.7 Gb file and set Copy to a temp directory. When I came back after awhile?

Error Code 0xC00D426A

OK let's see what happens when using File Explorer all by itself - just in case. What did I get?

Transfer 99% complete with 390 Kb left then just sitting there completely dumb. So I just kill File Explorer while the 99% complete file has actually been copied over, it was a complete video file which ran OK from beginning to end.

Just imagine doing that with 400+ files? I have less trouble reading Linux data files from a PVR hard disk drive in Windows.

When I have time later today [Christmas Eve here] I'll try a few more times - if I actually have time.

What I don't know is what is the final software action in regular file copying which isn't being completed in the last microsecond. What are the mechanics of File Copy?

And if you Google Error Code 0xC00D426A? All you get are my complaints, including a pirated copy of my original complaint from the Microsoft Forum. Apparently nobody knows what 0xC00D426A is or why.

Back to the drawing board.