Announcing Windows 10 Insider Preview Skip Ahead Build 16362 for PC  

f14tomcat said:

This is a wild stab, but.....

I had some really weird issues with the On-Demand feature working right, kept wanting to download whole files, not place-holders. I uninstalled OneDrive completely (I used Revo to get the deep-down crap). Rebooted so all the in-use stuff could be deleted. Deleted the entire OneDrive folder from USERS. Went to OneDrive ONLINE, and on the left-hand side under PC, removed the PC name in question. Basically cut all ties with OneDrive and that OS and my MS acct. Installed OneDrive, assigned my MS acct to it, checked On-Demand option, picked all folders, and it set-up all place-holders and was done in about 10 seconds. Rebooted to make sure it would hold, and all is well.....so far.

YMMV..........

Well Flabber My Gast, this worked! I now have Files in Demand.

I think the trick is to deep clean the registry

If you come to Aberdeen, I'll take you to a Whisky bar to die for!

cereberus said:

Well Flabber My Gast, this worked! I now have Files in Demand.

I think the trick is to deep clean the registry

If you come to Aberdeen, I'll take you to a Whisky bar to die for!

It hides little flags down there that bite!

Glad you got it sorted!! :)

I really need somebody to even take a stab at this screenprint showing two instances of winver. The one on the right is from my physical machine which was a fresh install of 16362 from an ISO. The one on the right is a Hyper-V VM which just updated (and I'm pretty amazed at that) from 16353 to 16362. The first as you can see has an expiration date even though 10 months from now. The Hyper-V VM shows no expiration date.

martyfelker said:

I really need somebody to even take a stab at this screenprint showing two instances of winver. The one on the right is from my physical machine which was a fresh install of 16362 from an ISO. The one on the right is a Hyper-V VM which just updated (and I'm pretty amazed at that) from 16353 to 16362. The first as you can see has an expiration date even though 10 months from now. The Hyper-V VM shows no expiration date.

Which is which? Is the one on the right the one on the right, or is it the other one on the right? :)

The one on the left is the physical machine which was upgraded to 16362 from an ISO (took a chance and figured uuptoiso was cleaned) created in a VM. Note the expiration date of 7/2/2018. The one on the right is from a Hyper-V VM of 16353 which was upgraded to 16362. Note there is NO expiration date. Now it so happens that I "may" have successfully upgraded a Hyper-V VM or the physical machine running 16353. I used disk2vhd for this. It's at "working on updates 4% "and going very slowly. If it boots it will be interesting to see what that winver produces. Anybody else got a 16362 with no expiration date? That would seem to be a final release - exceot it states 1703. Quite strange.

Some games are kicking out of full screen and dropping to taskbar in this build. "Flying Tigers - Shadows Over China" is worst.

The Hyper-V VM created by disk2vhd upgraded "successfully" to 16362 from the original 16353 and winver showed the same as the physical machine with an expiration date of 7/22018. Why the quotes? Because this was the most bizarre upgrade eve. I wish I had a screen print of the original 16353 desktop but this new desktop looked exactly like a fresh install with the only exception that Start was still Start10 (but the Start 10 configuration was reset to factory!!). Nonetheless all the programs were seemingly still intact. Advanced System Care 11 found 2.2 GB of junk files but the registry was pretty clean with only 218 registry errors. I must say that I like the way the Windows Start Menu looks and am glad that Start 10 allows me to access it directly. A very interesting turn of event - I doubt I'll ever be able to explain it. But that's why I love this program.

Trouble on the home front here. Strange as it seems > I close all programs out using Alt/F4, then use the same key combo to shut down the PC as I've done on any machine for years. I noticed the other night that after I did I accidently hit a key and the system livened up as coming out of sleep. Sure enough, it wasn't shutting down but rather going to sleep. I then used the physical button and it shut down. This was in my CU partition.

Then I rebooted to my Insider partition and the same occurred. What the hay?!! I'm thinking this happened since this last update to 16362 on Wednesday and/or the CU cumulative update on Tuesday which I didn't perform until Wednesday.

What could possibly cause this?

Edit:

With experimenting some more, it seems the PC turns of using Alt/F4 and the physical power button, for when I use either one, then hit a key, it boots up to the boot menu, therefore I’ll have to assume it’s not sleeping. The keyboard and thumb drive lights go off as well. If I put it to sleep the thumb drive light goes off, but not the keyboard, which is understandable.

Unless this is some new feature, which I think it’s not, I’m stumped on this one. Any ideas?

martyfelker said:

Anybody else got a 16362 with no expiration date? That would seem to be a final release - exceot it states 1703.

Logics: there's no way a Skip Ahead build would make it to official 1709 release. It's absolutely clear that this current Skippy 16362 is not / will not be "RTM" of 1709, nor will any other Skippy build.

The official 1709 release will come from the normal Fast Ring fork, not from Skippy fork.

- I suspect that we skippers will know more after mid-October,
- when the need for a new branch will become more obviously slanted towards RS4

- quite rightly, Microsoft will be currently directing their focus on Fall Creator's Update
- the skippers might need to tread water for a while..

- patience is the watchword..