Issues Updating from 1703 to 1709

Hi Robert,

            Current version is 16.299.248 and the Update I am attempting to install will, I believe, take me to ---.309 after KB4088776.   On the issue of troubleshooting these updates, I made such a comment on Feedback when having trouble installing 1709, can't do piecemeal to narrow the problem to 1 area.  Seems a number of other people are having real problems with Delta Updates trashing their PC.

            Do not understand reference to Power Shell Pipeline fro Updates.  As I have Pro and have had problem with Updates awaiting Restart playing silly buggers with my PC I have "Download and notify for Install" selected. It use to be Notify to download + Notify for Install but the option has gone.

            Power Shell ? gives KB4053577 & KB4088785 on the 13th; KB4087256, on the 15th and KB4074588 & KB4074595 on the 16th. Is that what you wanted.

            Sorry but you lost me after Bold text except Winver.  The hyperlink at the end leads to a repeat page  from previously with a reference to Enterprise for my problem.

Will shortly run clean Boot and see what happens.

Hi PCR

        My setup is based on what were good practices advocated by many in the early days of XP.  I will not repeat my reason for using this type of setup.   Windows 10 allows what I do by providing the Options to do so and 16 years of shared Virt Memory (not currently) have had zero problems.  I no longer share the Software Partition as storage capacity has removed the need and I could see possible problems if continued with Win7.  Bar the Win 8 to 8.1 Update I have had no problems with Updates until the change to amalgamated Updates. 

       I had removed the HDD at one point in the 1709 Update problem to allow me to try using a DVD with an image of 1709 to get the Update installed but that failed and I then did a clean install of 1709 last month onto the SSD.   I tried every permutation possible to get 1709 installed without starting from scratch and I really cannot remember the detail of every change I made in the abortive attempt. At one point I did have the SSD in the Opt slot but changed that for the Clean install of 1709 I think.  During my attempts at 1709 I hid partitions to remove any possible confusion during install.   Before Virtualisation I had XP on multi boot and in later life some Updates had problems identifying which was the C:\ drive the Update belonged since all are C:\ when in use, the partition position did not always seem the relevant reference.

          Current best practices suggest it is inadvisable to have the Virt Mem on an SSD as it can severely shorten the drives life with frequent churning of content and at the moment SSD are to B expensive to waste.

          Regarding the Old Windows file, I think that was exactly my own question in relation to that.  I did not use a Wipe Data action for the previous files contained but I did change the partition size and format it.  I also selected "Retain Nothing" at install so your guess is as good as mine.  As I often repeat "Win 10 is an overgrown mammoth, too big for its own good and beyond the control of Microsoft at its current size, although it has shrunk a little of late but not to where I can back it up to one DVD as I could with XP.   I still fail to understand why the default for Windows is to mix everything up on one partition.  I should be one for the OS and another for all files belonging to a user be it .pst or anything else.  No more lost Address Books or whatever should the OS become a unusable or un-Updatable.  Do you put your bank details and passwords in with the washing, your clean clothes, your record collection, your food and anything else not for disposal, NO.

            You appear to be looking negatively for a get out answer to the problem.  Anything I do now may not be mainstream average User but do major businesses allow this mix for all User workstations and Data and storage?

Hi PCR,

   Further to some of the points I missed.  I have not FIDDLED with the boot menu but I have used EasyBCD to manage changes in the boot menu over the years.  Windows will only allow the most recent OS to rewrite the Boot.  

   It is impossible to itemise every method that I used to try to install 1709 and while I am sure there are inconsistencies in my numerous posts they are result of the multiple efforts I have made to install 1709 which I have tried to communicate with the limitations of using words to provide a description of every variation I tried.  If you consider the hours I spent over 3 months in my efforts to install 1709 then you may understand the lack of complete picture provided by my few hundreds of words.

=== I'm still puzzled with that. Did you actually have a Windows.old folder, or just a $Windows.~BT &/or a $Windows.~WS...?...     Yes, I removed the lot as junk once I knew I had a reliable 1709 installation.  Maybe you have no idea of the amount of junk that Windows Update can leave behind.  Why would I keep Windows Old when there was no Old Windows to get files from.    If you have wasted as many hours as I have chasing every possibility I can guarantee you will not be interested in going through 48GB remnants of crap, I finally had a usable 1709 Win 10 so should I really care about the garbage remaining?  Then I had the task of reinstalling one hell of a lot of Software after 3 months of every minute of my spare time in solving the Update problem.  Just like the time for my reply to your post which I assume you made in an effort to help me out of this Update failure. 

       I appreciate the effort but please do not nit pick the inconsistencies of my past posts as you see them when they related to a particular post and may therefore not be consistent with the total situation. When Windows allows a complete clip of a timeframe for any problem then maybe we will have a complete assessment available for analysis of any problem encountered in an Update.  At the moment the reporting of Update failures leave one hell of a lot to be desired.  The latest Update method may be applauded by many but is a nightmare to many others with problems caused by this "innovation" who are unable to localise the source of any problem/failure encountered.

Hi PCR again,

For clarity,

             Disc 0 is SSD 125GB with Win 10 Pro OS

             Disc 1 is HDD 1TB with everything other than main OS mounted in Optical Drive slot.  

Sorry if replies piecemeal but with this problem and dual responses plus being below par and being out of my depth has problems. 

             I  have done a lot of things with Windows but the latest problems are getting beyond any long term Users normal understanding of the OS.  Maybe the workings of Win 10 are just becoming so convoluted in the efforts to get Windows back under control that the problem for us Users with the resultant problems are becoming more than reasonably complicated.  For many years I just ran a Repair Install (my term) with XP for my OS and all was OK again.   Never a failed Update ( from a Service pack 1 or 2, 3 or whatever) and regardless of what I did to XP in my various experiments, which were many, I could easily fix a broken XP, I was always able to quickly mend the problem and regain a fully functional Win XP within minutes.  

            As an OS becomes more able then one expects a growth in size but why exponential, with learning & innovation there should be a sufficient reduction to enable a near equivalent size.   Why the need to carry drivers for all and sundry.  What is the point of a Windows installation wanting an internet connection for Updates and apparently ignoring all the Hardware drives etc updates needed.  I could be wrong in my understanding of the way things appear to be to me. Why does Windows want me to install the driver for hardware from my PC maker (like Dell) and then provide Updates for them which are generic and possibly wrong. as happened in the past for my AMD Graphics Card.

            Current version is 16.299.248 and the Update I am attempting to install will, I believe, take me to ---.309 after KB4088776.  

I think I would try installing the servicing stack update manually first.  I got it (a whole week) before the one you are heading towards and we saw in your diagnostics that there was something wrong being reported which involved it.  Maybe we can get some better diagnostics that way.  Maybe you'll get lucky and this will break the obstruction.

Here's the clue that this should work

"ImportantWhen installing both the servicing stack update and the latest cumulative update from the Microsoft Update Catalog, install the servicing stack update before you install the cumulative update."

Here's the Catalog search you could download from

https://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB4090914

Good luck

Robert