New
#120
Like most new features in the Dev channel, it is not available to everyone from the get-go. Some users have already seen it come and go. Personally I would not make much fuss about it.
Customization - How to Add or Remove News and Interests icon on Taskbar in Windows 10 | Windows Questions
I'll make a suggestion. Do if you want. It's harmless.
The ISO for this build is available (see top of page 1). DL it and run an In-place repair. Takes 30 mins or so, depending on your machine. That may tickle it to give you the feature. Nobody but MS knows what goofy A/B algorithms they are using.
Just a thought............
Last edited by f14tomcat; 09 Jan 2021 at 12:10.
Meaning no one really knows if this new feature is going to cut it to the Release Preview stage. MS is just probably testing it. So far, I have not seen it and I don't think I ever will since I am not an official insider. I got this build (Dev) from UUPDump and installed it in a Hyper-V VM.
As you can see, I succeeded in installing the 21286.1 build, finally... (Post above your last.) Yes, I've been on a previous build the whole time up to now! b20270.1 --never had a moment's trouble there. Every time the newer builds would fail, 20270.1 would be automatically reinstalled--didn't have to restore it from a backup.
Thinking on this overnight, it's possible that some kind of bizarre bug had developed in 20270.1 that was causing these problems, despite using sfc and dism routines to correct any problems! I don't know what happened, precisely, that changed things simply because I installed the iso from my boot drive instead of another data drive--but apparently doing so fixed something that had gone awry in my 20270.1 installation (I guess it wasn't so "sweet" after all.)
One thing I noticed in 20270.1, too, was that suddenly my drive order beginning with drive 0 had reversed (In Computer Management/Disk Management)! Suddenly, my non-booting Sata3 data drives were enumerated first--one of the HDD's being drive 0 followed by the rest of the Hard drives--and the two NVMe drives were at the bottom as drive 6 and drive 7. Usually, my boot drive--1st NVMe slot--is drive 0. Did some light reading on it and apparently the consensus is that it doesn't particularly matter if Windows10 sees that order, and as the system was booting as usual from the NVMe boot drive, I didn't much think about it anymore.
But now that 21286.1 has installed, the drive order in Computer Management/Disk management has returned to normal. 1st NVME drive, boot drive, is now drive 0, followed by NVMe #2 as drive 1, followed by the remaining Sata 3 HD's in the system in the order of their port assignments. Go figure. So maybe the correct installation of 21286.1 has fixed the entirety of the problem I was having.
In five years+ of being an insider, this is the worst *bug* I've seen yet. But, I guess if I didn't like this sort of thing I wouldn't be an Insider, eh?...Whew...
I made an unfortunate (but interesting) error on 21270.1 - installing an AMD Driver and forgetting I now had a Nvidia graphics card installed. O well - I will install 21286 as a new installation. It's a New Year. Just a few more days in the States and we should be out of the dark woods.