WDBackupService.exe - Application Error

Caledon Ken said:

Yes by all means I would do the scan.

I think the idea of the clean boot is to disable all third party software and services except WD. Then I would reboot. Windows and the WD software should be running. Then do what ever you do to cause the failure. If it does not fail you add x number of programs and try again.

If it fails you know there is a conflict within the group you added back.

Let's see what the scan yields.

When I search that error code within WD's forum there is an immediate hit with no solution.

The scan did not find any issues.

Caledon Ken said:

Morning Jesse.

Well good to know Windows isn't causing issues.

So in your original post you said you log off and then shutdown. What happens if you just shutdown without logging off.

@Caledon Ken, yes that's correct. Shut down is the same. The same message appears.

Caledon Ken said:

Okay then lets see if it related to Fast Startup.

Next time you shutdown please hold the shift key down before clicking shutdown. This bypasses the process for saving information for Windows Fast Startup up.

Just tried what you said to do, and it still did it.

My two pence if I may: I did use this software when I got myself My Cloud back in 2013 - and I found it horrible, buggy, resource-demanding and very patchy then.

Having fought a bit with it I just stopped using it, and decided to use File History that's built into Windows - that mirror all folders I care about to network share (=said My Cloud, that's connected to my router at home).

And that works a treat - and on two separate machines. I have daily sync put in place - could be hourly or every 10 mins if you want? And only need to purge old copies on a monthly basis (along my monthly backups). And it's free!

Perhaps worth considering?

WD BACKUP 0xc0000142 error after shutdown or restart WINDOWS 10 PRO 64 bit - WD Software - WD Community

Nah

Update: File History is back in Windows 10 build 16226.

Windows 10 File History backup feature makes a welcome return in Insider Build 16226
Windows 10t going to die after all - MSPoweruser

I daresay it's well alive and kicking.

So, what's the culprit? What should I do?