New
#150
Thanks, Cyberrufus: Putting the "path-to-.cab" in quotes seems to be working, and despite some other posts, the full file name--that is NOT deleting the Windows10.0-KB.......etc. start of the file name apparently is a key in getting the path to be recognized. We'll see, it's cooking now.
UPDATE:
Well, same result. The process worked seamlessly, allowed the update to download 100%, but failed on the install, and rolled back. At least your solution allowed a direct install outside of the Windows Update function in W10.
I believe that the problem stems from a corrupted Win Update database, created likely by a prior update and so far, no solutions are out there for that. The Wizards of Microsoft need to come out from behind the curtain to solve this one, which is plaguing lots of us and is widely reported in blogs, posts and forums all over the Web. In any case, thanks for the DISM structure so that we could test it for a better outcome. Appreciate your post.
Last edited by mhixson; 30 Sep 2016 at 20:15.
Yeah, this having to watch spinning dots every time I need to shutdown/reboot my machine is a PITA. I finally used the hide update tool.
https://support.microsoft.com/en-us/kb/3183922
.
Big FAIL MS. Two days out to Insiders is not long enough.
This OS has been another major flop for Microsoft. They claim this is the best windows ever? I guess all the noobs at Microsoft never used XP or 7. I have had way too many issues with failed updates and corrupt files over the past year. They can't even get basic functions working 100% of the time. Pathetic.
New update fail installation to me. I'm not an Insider at this moment.
I tried to install from cab too but without result. When seems it's done the installation roolback the current version (187). Now I'm using the 'show or hide updates' tool to avoid new attempts
Last edited by red5goahead; 01 Oct 2016 at 04:21.