Selective Startup 1607 RS1

Discussion in 'Windows 10' started by rockyanexpert, Aug 3, 2016.

  1. rockyanexpert

    rockyanexpert MDL Junior Member

    Mar 6, 2010
    78
    55
    0
    #1 rockyanexpert, Aug 3, 2016
    Last edited: Aug 3, 2016
    Some Observations:
    I did 10586.499 upgrade (MS Update)
    * Everything seemed to work fine but office 2016 got deactivated.
    * Startup mode: "Selective Startup.".

    Than restored v10586.499 and upgraded from iso created with Media Creation Tool.
    * Everything seemed to work fine but office 2016 got deactivated.
    * Startup mode: "Selective Startup.".
    ....Again

    Fresh installed from the same iso
    * Startup mode: "Selective Startup."
    (Even before installing drivers)

    No problem in activation.

    10586.499 was starting in normal mode. Why is this version always start in "Selective Startup" mode?
    Any idea?
     
  2. T-S

    T-S MDL Guru

    Dec 14, 2012
    3,988
    1,305
    120
    Msconfig ?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. rockyanexpert

    rockyanexpert MDL Junior Member

    Mar 6, 2010
    78
    55
    0
    Yeah.
    Done everything
    Booted safe mode
    Rebooted Normal Mode
    Still "Selective Startup"!!!!!
     
  4. T-S

    T-S MDL Guru

    Dec 14, 2012
    3,988
    1,305
    120
    Try to use easybcd, add your installation as a new item, set it as default and reboot.

    If it work open esybcd again and remove the old item
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. Flipp3r

    Flipp3r MDL Expert

    Feb 11, 2009
    1,477
    627
    60
    5 new installs, only 1 has Normal Startup. If you select Normal & reboot it remains Selective.
    Everything is running though...
     
  6. rockyanexpert

    rockyanexpert MDL Junior Member

    Mar 6, 2010
    78
    55
    0
    The problem solved itself automatically after a few (4-5) random restarts!
     
  7. maestrosir

    maestrosir MDL Junior Member

    Aug 1, 2016
    65
    43
    0
    It looks like just a bug.
     
  8. PhaseDoubt

    PhaseDoubt MDL Expert

    Dec 24, 2011
    1,448
    278
    60

    Maybe the "fresh install" just needed time to run through all its initial startup protocols.