Build 14366 Released

[Gideon]

http://www.neowin.net/news/here039s...till-broken-in-windows-10-for-pcs-build-14366

Microsoft today released Windows 10 for PCs build 14366 to the Fast ring. The build only contained a couple new features; however, Dona Sarkar - the new head of the Insider Program and replacement for Gabe Aul - writes up the fixes and known issues differently from her predecessor.

Rather than publishing a list of fixes, we now see a list of "Improvements and fixes". These aren't just bugs that got squashed. Some of them are useful new features.

Here's are the improvements and fixes for Windows 10 for PCs build 14366:

• For you mes amis: If you have a French Windows 10 Insider Preview build installed on your PC, you should receive this build as we have fixed the issue with the French translation process that caused a lot of text to revert from French back to English.
  
  
• Navigating to the Privacy pages in Settings app will no longer crash the Settings app and prevent you from adjusting your privacy settings.
  
  
• We have fixed the issue causing PC and Mobile devices trying to project to a PC (via the new PC Access feature) to fail.
  
  
• We fixed the issue where Start would not launch while an app is installing for certain languages, such as Chinese or Portuguese (Brazil).
  
  
• We’ve updated the size of the Windows Ink Workspace icon in the notification area on the taskbar to be more consistent with the other notification area icons. In a similar drive to improve the consistency of our experience, we’ve updated the X to leave the Windows Ink Workspace which will now show a red state when you hover over it. We also fixed an issue where mouse wheel scrolling wouldn’t work to spin the ruler with certain mice, and an issue where dismissing the share pane or accepting the prompt to enter tablet mode would result in exiting the Windows Ink Workspace.
  
  
• We have updated Cortana search results, so now when you right-click on a .docx file, you’ll see a context menu option to open that file’s location.
  
  
• We fixed an issue resulting in the monitors in under Settings > System > Display from sometimes jumping to a different ordering after being clicked and causing scaling changes. We also fixed an issue where the slider to change display scaling might jump to an unexpected scale factor as you were moving it.
  
  
• We fixed an issue resulting in not being able to unsnap a full screen Remote Desktop window if you had been prompted credentials while connecting.
  
  
• We fixed an issue when the tile names could become cut off after using semantic zoom, and one where Start tiles could no longer be moved with touch.
  
  
• In an effort to improve visibility and access to your newly installed apps, we have moved the “Recently added” section of Start to be located above the “Most used” section in the All apps list. We’ve also increased the duration of time in which apps will be listed here – now 7 days, so you can easily try them out and decide if you want to pin them to Start or the taskbar for regular use and quick access.
  
  
• We fixed an issue where an active VPN connection could block the PC from going from idle into sleep.
  
  
• We fixed an issue where the touch keyboard might appear on the Lock screen after pressing the Num-Lock key on the keyboard.
  
  
• We fixed an issue that could result in Microsoft Edge using a large amount of CPU when open to a page with many animated gifs, as well as an issue resulting in certain captchas not displaying correctly.
  
  
• From this build on your default location will now be preserved across build updates.
  
  
• We fixed an issue resulting in nothing happening if you attempted to expand a Skype notification in Action Center. We also fixed an issue where the scrollbar would draw with no margin from the chevron and X in Action Center notifications, and one where app logos might be missing from the Action Center.
  
  
• We fixed an issue resulting in the cursor not showing up when interacting with the system using a Wacom tablet.
  
  
• We fixed an issue where the Settings app could open to a blank page after selecting a settings page via search results.
  
  
• We fixed an issue where the File Explorer window might navigate back to Quick Access after deleting something from the current folder in view. We also fixed an issue where right-clicking on the desktop might result in showing a spinning curser for a long time before the context menu would show.
  
  
• We fixed an issue resulting in existing reminders failing to display in the Cortana UI, and an error when attempting to save a new reminder.
  
  
• We have updated the Mobile Hotspot settings page to allow name, IP address, and mac address to be selectable so it can be copied elsewhere if needed.
  
  
• We fixed an issue where the battery flyout might not report the correct overall charging state for devices with two batteries.
  
  
• We fixed an issue where the title bars of apps using dark theme wouldn’t be dark when the window was not in focus, for example, Groove Music or Settings app.
  
  
• We fixed an issue resulting in you sometimes seeing a progress indicator before the background image would load on the Lock screen.
  

Here are the known issues:

• The Desktop App Converter Preview (Project Centennial) will fail to run on the Windows 10 Insider Preview Build 14366. If you are a developer utilizing the converter tool to convert your desktop app to UWP, we suggest skipping Build 14366 or switching to the Slow ring until we can fix this issue.
  
  
• If you click on a file download link outside of Microsoft Edge, sometimes Edge will open a tab and close it without doing anything. The workaround is to go to the Download pane and start the download there by clicking “Save” or “Save As”.
  
  
• Narrator does not launch when you toggle switch to “on” via Settings app > Ease of access > Narrator.
  

There are only three known issues, which is good news since the Anniversary Update is only about a month away. Of course, it wouldn't be surprising to see some get added to the list as time goes on.

If you're on the Fast ring, you can get the new build by going to Settings -> Update & security -> Windows Update -> Check for updates. If you're not on the Fast ring yet, you'll need to go to Wndows Update -> Advanced options and turn on Insider builds. Once your PC reboots, set it to the Fast ring. Keep in mind that it might take about 24 hours before you see a build.

 

[Norton]

Wow! That's a lot of bugs.

 

[Trouble]

Installing now.

Wow! That's a lot of bugs.

Only three remaining "known issues" on the PC Build, so that doesn't seem too bad.
These builds seem to come when I'm at my busiest.
In the mean time, it being update Tuesday, I've downloaded and installed the updates for my 10586 machine
Cumulative Update for Windows 10 Version 1511 for x64-based Systems (KB3163018) and Update for Windows 10 Version 1511 for x64-based Systems (KB3149135) with MSRT and a couple for my Office install.

 

[clifford_cooley]

Have they posted when they will make another public release build? Is that what the Anniversary update is in reference to?

 

[Tim Locke]

I missed the announcement as I don't have a Twitter device near my TV! Tomorrow. I looked at the list above and I have to say I had not come across any of them...good thing they don't pay Insiders buy the bug report.

 

[Trouble]

Have they posted when they will make another public release build? Is that what the Anniversary update is in reference to?

This one seems to be all about the current "bug bash" project, a four day deal that is suppose to conclude Sunday so.....
It wouldn't surprise me, if they release one shortly thereafter as a result of their findings.
Not a whole lot of time before the Anniversary Update which is suppose to be released late this month or early next month. I noticed they still carefully say "this summer" and nothing more specific than that.

 

[Tim Locke]

I bet they want it out while the upgrade to W10 is still free.

 

[davehc]

"Not a whole lot of time before the Anniversary Update which is suppose to be released late this month or early next month"
I did read a rumour, Trouble, somewhere in the MVP archives I think, That the release is delayed quite a bit. I'll try and find it. - But with the way MS distribute info these days, it is thát - a rumour.

 

[davehc]

This one seemed to work like a complete reinstall.

It would be really interesting tome, if they could clarify where, when an how those "fixed" faults have been occurring. I have not experienced an of them.

 

[Trouble]

I did read a rumour, Trouble, somewhere in the MVP archives I think, That the release is delayed quite a bit. I'll try and find it.

Wave two (2) of the Redstone release which was scheduled for this fall, definitely got pushed to 2017.
I hadn't heard anything about this first part being delayed, except they seem to switch the rumor mill back and forth between June and July.
I kinda agree with Tim.... I suspect they want something out there before the July 29th cut off. Frankly I'm surprised that they aren't pushing to target Dads and Grads.
I just ordered a new laptop for my oldest grand daughter who just graduated high school and will be headed off to college in the fall. Wonder what version of 10 will come on that.... probably 10240 knowing Dell.

 

[Tim Locke]

It will probably come with 10586-386.



It does worry me that there are still posts like the one from Devenish today. The simplest things...Occams razor... are that the upgrade did not download correctly. Either Windows update is not checking the data correctly. OR that there is something like an out of date AV program on his machine that is killing something vital.... My point is that that stuff like his problems should NOT HAPPEN without a sensible error message and a choice whether to give up or retry,. I wonder why neither of these things are implemented.

 

[davehc]

There can sometimes be good reasons,which may not be errors on the part of Microsoft, but through users attempting adjustments through the group policy editor or more directly in the registry itself.. Whilst such hacks often satisfy the immediate problem, they may impact the performance of other items.
To date, apart from small problems, often associated with the above, I have had nothing serious happening with updates or overall performance..
At this moment, I am using an old Acer with a dual core CPU and 3gbs of memory.. This is my sacrificial computer, which I leave running, to accommodate the update strategy imposed on us.

In the post you mention (First and only post from the member) I do not see it as a faulty download,
a very flaky OS or installed software

I should add though, that I am very dissatisfied with the update system. I was actually making a post in the early hours today, when the accumulated update arrived. On my 3mb connection, this put me out of commission for about 30 minutes.
I am satisfied with the present state of Windows 10. Security updates for defender are welcome. I have no requirement for any further upgrades/updates, beyond that, unless, as in previous OS's I decide to take the plunge and go for it.
PS This is not the subject of the build updates which come regularly, and for which the user can volunteer or drop out.

 

[Trouble]

I wonder why neither of these things are implemented.

Good question.
But, this is not something new. I have been doing this as a source of income for a very long time and even though retired, I still find myself helping family, friends, neighbors and a buddy who owns a couple computer stores / businesses.
I can tell you that when Windows '8' (not 8.1) first arrived on the scene, I was never, ever able to upgrade my then Windows 7 Pro 64 bit computer successfully.
It failed multiple times (3 I think before I gave up). Nothing catastrophic happened, as it reverted back each time. This all happened over a period of weeks and some due diligence on my part, checking logs, etc., to see what was failing. I finally gave up on the upgrade and did a clean install. Another not so easy feat, doing a clean install from Upgrade Media (that's all that was available the time, they had some special deal where you could purchase upgrade media for $14 or $15 bucks at the time).
Upgrades are great when they work, but they've been failing for any number of reasons (some self inflicted) for a long time.

 

[Tim Locke]

Dave. Why would one suspect the Group Policy Editor. Unless some of these people are or have been in a Domain, knowingly or just from logging on to a work network from home. Now I appreciate that the GPE can interfere with Insider builds as they are W10 pro. but your basic W7 home premium I think doesn't have GPE. But maybe more people bought W7 pro. I don't know about the various varieties of W8/8.1 as I managed to avoid it!

Trouble. I see your point about W8. But MS have had 11 months ( plus Insider time) to master the upgrade procedure for W10. Neither I nor my buddies that have done W10 upgrades had any problems and I am sure some of that was good luck and some was making sure McAfee, Norton or AVG were de-installed before the upgarde and, if they insisted , put back well after the first 2-3 boots with the new OS.

 

[Trouble]

making sure McAfee, Norton or AVG were de-installed before the upgarde

Excellent advice.
I would add all the other third party security suites to that as well.

 

[davehc]

Sorry. Not sure what point you are making regarding the group policy, naturally, my reference was broad and would only refer to those who can open it. As you know, indirectly, the GPE is a graphical means of getting to most parts of the registry. Any changes done there are reflected in the registry. Could be why, from the word go, it has never been available to the home user, on the very wrong assumption that anyone with a pro edition, has more savvy.

 

[Gideon]

Wow! That's a lot of bugs.

Yes and they were all fixed. The final RS1 version release of 1607 will be in less than one month. The build 14366 is now version 1607 if you run Winver. I do not understand all of this talk about Group Policy which is in Win 10 Pro and third party AV's. They do more harm than good. Windows Defender now is as good as Avast Internet Security that I still have a license till 02.2017.
WD plus windows Firewall does the job.

 

[Tim Locke]

Dave I think the assumption is that the Pro versions will be in a domain and the Domain server will deal with policies AND lock it down so that users cannot use it.

 

[davehc]

Tks for the response. I am afraid I do not quite follow (getting too old!). GPE has always been in the Pro, which was just the same OS but with more facilities .It has been possible to join a domain - if you wished, which was not available in the home edition, of course.
I no longer keep as up to date as once, but has there been any comments or blogs that it will be mandatory to belong to a domain with Pro?


I have always used the Pro editions, since the first was available, but, in my case, apart from the long-time hobby of trying to help others, the Home edition would have satisfied my domestic requirements.
Perhaps a good time, for others to read, this: