Issues Updating from 1703 to 1709

Hi Robert,

     Having started a Clean Boot I found that Updated wanted to just restart the search for new updates.  Having rebooted I am no longer able to get into Windows from the login screen, no box for Pin or Password.  I am in 1703 just now and about to bash my head against the wall in the hope something will rattle loose and enable me to get back to my SSD Win 10.   F8 does nothing for some reason so no access to a Automated Repair.

       Think I will download latest image including KB4088776 and try from there BUT 1703 is currently wanting to install 5 Updates over which I have no control.  This bloody enforced download of Updates is a nightmare when one encounters any sort of Update problem with Updates.  How can one sort one problem when **** is being dumped on top of your effort to dig yourself out of the existing problem.

        I appreciate Updates are needed but this way of providing them is ridiculous, does a drowning man need more water?

Having installed the 5 Updates my 1703 Windows has gone directly into a non specific Update to 1709 which I suppose I may as well allow to continue as it is already 50% downloaded.

What the F have I done to Microsoft that it keeps pissing on everything in an attempt to F up my OS and waste my and your time like this??

 no box for Pin or Password.

One possible reason is having an Accessibility tool active and with focus.  For example, this happens to me when I leave the On-Screen Keyboard running.  Then all you would need to do is press Alt-Tab to switch to the Login screen task and then you will be able to raise your Input frame.

It sounds good that 5 updates have installed. Fingers crossed that v.1709 will come in well. Good luck.

Here's what I was working on before the recent developments...

(1) I mainly complain of the Windows Temp folder(s), such as C:\Windows\Temp. I think each Windows installation best have its own. Also, even in a single installation, Windows or a 3rd-party app may not honor the move.

(2) I'd still like to see the DiskPart listing itself. But what matters is...

(a) Does an HDD/SSD have to be Disk 0 for (some) Windows updates/upgrades to work?

(b) What are the consequences of installing Windows onto a partition on Disk 0, then switching things around so that it becomes Disk 1?

Edit: At an administrator Command Prompt or PowerShell, let's see...

BCDEdit  /Enum  All

Click the icon in the Shell's header, & use the Edit menu to copy/paste the result here.

HI PCR, 

   Out of all the permutations I used it is a problem to get straight exactly what the sequence was.  Yes, I installed 1709 on the HDD but in the end I did a Clean Install on the SSD of 1709, there is just too much history to repeat as the between steps.

        1709 was installed on the 0 drive which was the SSD and the original Win 10 1703 (and 1709 from which the clone below originated) in that location moved to the Optical Drive location .  I had cloned 1709 to the SSD but despite modifying the registry it was still recognised as a usb drive for GKW reason, I certainly do not.   To cure this problem I changed the partition size and formatted the drive and installed Win 10 Pro 1709 SAVING NOTHING. 

        The more you dig around this I am sure the more confused you will become as I have enough problem keeping trace of the convolutions:  All that matters is that my current 1709 version on the SSD in the 0 Drive location is a Clean Install to that drive in that location as I have repeatedly stated.