14279-Win Resource Protection Couldn't Start Repair Service

You may have to roll back to the previous build if wasn't a clean install made by way of ESD to ISO conversion. It sounds a bit more like the upgrade by updates that comes out buggy. The Refresh option wouldn't be available until the upgrade was completed which sounds too much like it wasn't.

One option I found useful here for getting things done faster was the get the Threshold 2 Update on clean and then enabled the Get insider builds option to allow the upgrade to take place from the clean install. The 14729 is now flying on not only the second desktop in no time but the second VM is now updating being the 3rd in a row in just a few hours time without seeing any problems. The second desktop with the TH2 was off during the month of January before seeing the 14257 replace the TH2 which then saw the 14267 replaced in a few days by the 14271 just replaced by this latest 14279 build. A clean install now if not able to roll back would see the second opt for the 14279 most likely go well.

Well that will be the inplace upgrade to repair type of install there. But you might want to plan a full clean install after seeing the 10 media made up fresh just in case the first conversion wasn't complete. Or try using a different flash drive. Seen that happen at times where an iso had to be rewritten to a good flash drive a few more times just to get it to take!

One option like I was saying would be take the Media Creation tool and download the TH2 twice one for the 8gb flash drive you will need for the "4 in 1" iso that is being both Home and Pro in both 32/64 flavors explaining the 5.48gb on disk size and go for the Insider builds. The first you will see will be the latest now seen 14279 just out. Then you can grab either the install.esd or install.wim file which I ended up seeing here to keep on hand. Of course then the next Insider build will be at the start of April if not sooner?!

I think going backwards a few steps to the Threshold 2 and seeing that updated to the 14279 will be what will work. I've done that on a few test VMs and so far at least on VM the results having going steady for each new build considering I leaped forward right over a few builds when holding off on upgrading over the TH2 on everything. That includes the main build's main drive as well as the main drive on the second test build there seeing favorable results.

Once everything was past the 10240, 10565, 10576 builds onto the 10586 Insider to TH2 the upgrades have been going well. The TH2 getting fuzzy on the main when not able to fix a renaming folders problem was solved with the 14267 rather quickly being the only glitch seen lately. I'll be seeing how the latest goes by keeping that on now for a few more builds while the second pc and VMs continue on.

Upon seeing the latest go on the main build's C drive and watching as the upgrade to the 14279 froze at 32% forcing a hard boot for an unknown reason and rolling back I was browsing the "$Windows~..." BT and WS folders I have been finding for the 64bit Pro but not for the 64bit Home upgrade by update as well as previously seen clean installs. With the Home edition on VM only that will see the BT folder only.

One trick to getting around the need to write an iso to a flash drive is once you have the flash drive made bootable such as using the Media Creation tool to create the TH2 stick and then wipe the folders/files off manually except what is seen at the root directory you then simply copy the contents of the BT folder right after an upgrade by the WU is seen.



You can use the files as well as sub folders from the BT folder to replace what is cleared off of an older build's usb install much like we saw 4 in 1 keys made only this works for one build's edition(Home or Pro) and flavor(32/64bit) only. The setup.exe is started while booted in Windows however for the upgrade type of install either for seeing the newer build go on or for an inplace upgrade to repair.

For you that would mean not even worrying about the media as long as the BT or WS folder saw the same files. It wouldn't be a clean install but the upgrade over the previous build only not through the Windows Update method.