Windows 10: Announcing Windows 10 Insider Preview Build 14955 for Mobile and PC

while waiting for the latest insider build for mobile....

- switched over to the slow ring
- altered the date to a week ahead
- checked again for updates..

- lo and behold, the 14955 update started up..!! *Confused

- the installation is at 45%
- don't think it will complete, with wrong date.. *Confused

EDIT: UPDATE - it completed - restarted and fully installed..
- I went back and corrected the date
- then I re-joined the fast ring..

- now I'm double-confused
- why did that work..?? *Confused*Confused*Shock

 

Notice please, this don't have to apply to all of you geeks but I have noticed that sometimes I have wrong values in registry, comparing for instance two almost identical Insider machines, one getting Insider and the other not.

These are in my case correct Fast Ring values in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability:





FlightingOwnerSID is of course individual, your Insider Microsoft account SID on that specific machine, do not change it in any case!

When checking the problematic machine registry I've sometimes had EnablePreviewBuilds DWORD as 1, sometimes 0, and IsRetailOS has sometimes been 1.

As soon as I have fixed these values and restarted I have most often than not got the upgrade.

 

Update:

Tweet



— Twitter API (@user) date[/quote]

 

hi folks,

I've been away for a while and I was just peeking and checking out some stuffs here from time to time. Since I came back early this month, I haven't been able to get any of the latest Insider releases. I am still on 14393. I think I need to do a clean install and start somewhere again. Which version (available for download) should I install that I can get updated to this latest Insider update? Thanks!

 

What I do is clean install the AU, join the Insider Fast ring, and wait for like (max) 48 hours. Then it gets me the latest Insider build. And always in a dedicated SSD, the only drive plugged into my system during installation.

 

with this update, my PC doesn't shutdown, it always reboots

 

You mean it keeps rebooting even after shutdown attempts?

 

Run this line in command prompt (as Administrator)
%windir%\System32\shutdown.exe -s -f -t 00
and see if that helps.

 

yes that's it

 

Did you run that line I told you about ?

 

I have one low end Asus laptop with similar issues since 10XXX builds. I have completely given up and accepted its behaviour as nothing I will do will help. This is how it goes with Fast Boot in UEFI settings enabled and disabled:

Fast Boot disabled:

• Shut down works if done within a few minutes of boot (varies, sometimes I can shut down normally for up to 30 minutes after boot, sometimes shut down stops working already after 5 minutes)
• If shut down is done later, it will reboot
• Restart works normally
• Because of the above, when I want to shut down when laptop has been on a longer time, I need to restart it first, wait until it boots back to login screen and then select shut down which now works normally

Fast Boot enabled:

• Shut down works partially leaving the power indicator on meaning shutdown is not complete, holding down the power button takes care of that
• Selecting Restart will shutdown the laptop
• For instance when a build upgrade needs a restart, laptop shuts down instead of a restart and I need to continue upgrade by manually turning it on again

I do not think it will help in this case. I've tried every possible way to work around the above mentioned issues. No method to manually shut down works.

 

still no update here





what is the ring backup

 

Have you tried right clicking start and use "Shutdown or Sign out"?

 

After yesterdays update 14955, my package also included the latest Adobe Flash Player KB3201860, which according to the log, installed successfully. Today I am getting pestered from Adobe wanting to install the latest update. Has there been an update since yesterday that has not made it to WU yet?

 

I would delete that string value from registry, it is most definitely not needed.