Dump it and call it a day! Grab the MC tool to download the TH2 and let that upgrade to the latest! Whenever I run into anything that stubborn I take a look at possibly seeing it replaced. I had a 10586 Insider VM that didn't upgrade to the 14267 lately and soon after DID upgrade to the 14271.
Why? It had to finish installing all of the latest updates including one stubborn to go Windows Defender update! Once one zamooooooo... !!! 14271 rushed on like lightning already ready to download when rechecking on where the Advanced setting were set. It wasn't! Back in December I was planning to keep the 10586 upgraded to TH2 running on that VM while pushing the second 10 Pro and another 10 Home VM on the other machine pushing ahead.
You are likely running into the exact type of problem if you installed any 3rd party av or firewall app there! That will need to be disabled while checking the updates again to insure any loose uninstalled go on and then watch the latest arrive!
I didn't have a chance to even take notice at the time since the Insider builds were either the host drive on the second machine used for testing or on one of the VMs being run on the 7 side of the dual boots I have going here. The one thing I did notice in particular at the time however was how smoothly the upgrades by updates went on for the TH2 and still go smooth as silk for the latest builds in comparison to the early buggy upgrades seen between the July 29th 10240 release and the 10565.
The hangups I kept running into on one VM while only a delay on the second newer 10 Pro VM but not on the 10 Home VM was the first 10 Pro VM first not being enabled and secondly the few updates that were failing to go on or incomplete. For a month having the second build turned off keeping the TH2 intact I ended up skipping past a couple of builds until trying to get the 14267 on! That's when the fun began with updates again.
The first VM this time was watched as well as the TH2 on the main build's host drive where the av software was preventing the WD update from going on earlier. And once that was turned off zzzzzing on went the WD and all set from there.
Once you removed Malwarebytes you allowed the latest WD update to go on which tends to proceed each new build seen since the TH2! I shutdown VIPRE here to see the latest go on three separate VMs while forgetting to shut the av down on the second machine which was actually the first to see the lastest go right on. For someone else however trying to clean install from converting the install.esd file to an iso the clean install came out bugged and had to be dumped where the suggestion was then made to upgrading over a previous build that would go on since the continual upgrades since the 10586 Insider have been going smooth here each time.