Forum Discussion
HotCakeX
Mar 18, 2020MVP
Announcing Windows 10 Insider Preview Build 19587
Hello Windows Insiders, today we’re releasing Windows 10 Insider Preview Build 19587 to Windows Insiders in the Fast ring.
Spoiler
General changes & improvements
- Based on feedback, when you have muted your volume, the volume will now not unmute when using the hardware keyboard volume keys until you raise the volume (or manually unmute).
- We made a couple of improvements to Narrator and how it works with some of the controls in Windows:
- Narrator now uses a more friendly string to describe the audio output in the Select playback device dropdown menu in the volume flyout.
- Narrator now announces more information in the Add Bluetooth or other devices dialog in the Settings application when first opened.
Fixes
- We fixed an issue where the new icon next to Scan with Microsoft Defender in File Explorer’s context menu didn’t have a transparent background.
- We fixed an issue that could result in Default Apps page in Settings crashing when you tried to change defaults.
- We fixed an issue that could result in the search box being missing from certain apps.
- We fixed an issue where some files couldn’t be opened in win32 apps from File Explorer when the path length to the file was very long and parts of the path included East Asian characters.
- We fixed an issue where thumbnails weren’t being generated for pictures inside a Work Folder.
- We fixed an issue where adding the Session column to the Users tab in Task Manager would result in not being able to expand the details for a particular user.
Known issues
- We’re blocking this build from ARM devices because of an issue causing them to receive a bugcheck.
- BattlEye and Microsoft have found incompatibility issues due to changes in the operating system between some Insider Preview builds and certain versions of BattlEye anti-cheat software. To safeguard Insiders who might have these versions installed on their PC, we have applied a compatibility hold on these devices from being offered affected builds of Windows Insider Preview. See this article for details.
- We are aware Narrator and NVDA users that seek the latest release of Microsoft Edge based on Chromium may experience some difficulty when navigating and reading certain web content. Narrator, NVDA and the Edge teams are aware of these issues. Users of legacy Microsoft Edge will not be affected. NVAccess has released a NVDA 2019.3 that resolves the known issue with Edge.
- We’re looking into reports of the update process hanging for extended periods of time when attempting to install a new build.
- Some devices may experience a bugcheck (GSOD) during the reboot to install this update. If this happens, log in, schedule a time for the update to install, and then log off all user profiles before the scheduled install time. The install will then proceed as expected.
- The Documents section under Privacy has a broken icon (just a rectangle).
- When trying to use Win + PrtScn to capture a screenshot, the image is not saved to the Screenshots directory. For now, you’ll need to use one of the other options for taking screenshots, such as WIN + Shift + S.
- We’re looking into reports where, when running corruption repair (DISM), the process will stop at 84.9%.
- We’re investigating reports that Sticky Notes windows cannot be moved on the desktop. As a workaround, when you set focus to Sticky Notes, press Alt+Space. This will bring up a menu that contains a Move option. Select it, then you should be able to use either the arrow keys or the mouse to move the window.
- Ian_SalgadoCopper ContributorI'm currently running windows 10 insider preview build 19536 PreRelease 191211-1446.
I'm trying to upgrade to the latest release preview 19587
I'm able to start the process using the normal windows updates, the files download without issue & installation start. The install process gets to 62% completion & then stops...
It does not continues at all & even if you wait for hours, it does not work.
Any ideas ?- Spoiler
Ian_Salgado wrote:
I'm currently running windows 10 insider preview build 19536 PreRelease 191211-1446.
I'm trying to upgrade to the latest release preview 19587
I'm able to start the process using the normal windows updates, the files download without issue & installation start. The install process gets to 62% completion & then stops...
It does not continues at all & even if you wait for hours, it does not work.
Any ideas ?All i can think of right now is that you're probably experiencing this know issue..
"We’re looking into reports of the update process hanging for extended periods of time when attempting to install a new build."
- RedBetaIron Contributor
You can try the following:
Command Prompt with Administrator privileges...
type reagentc /info
In my case Windows RE status: was disabled / missing.
I had to find a copy (on the local hard disk) and then enable it....after that I was able to install new builds.
- Ian_SalgadoCopper Contributor
yep tried that already. It was enabled
issue still persist.
I even tried resetting the SoftwareDistribution folder (a couple of times) but no luck with that either
- StephenWhiteD3GIron Contributor
Just to note - this update (like the last 2-3) is wreaking havoc with certain WPF applications (Visual Studio being one of them) when it comes to mouse click detection.
Also I noticed that ever since updating to it, I seem to have problems with VPN connections (Rasphone or the Windows 10 wrapper). I tried doing all of the usual troubleshooting steps (rebuilding the VPN connection, refreshing my IP address, etc) but something is causing fatal errors when creating the TLS client credentials. This wasn't a problem with the previous build on the fast ring. I'm going to wait and see if the next update fixes this before trying anything else.Edit: Disregard the note about VPNs, see my newer reply below.- Hi, which VPN protocol do you use?
I use SSTP and PPTP, added them to the Windows 10 from settings rather than using .pbk file, it's working fine- StephenWhiteD3GIron ContributorHotCakeX
I stand corrected; the update didn't break anything. My VPN tunnel actually does work, but for whatever reason it isn't letting me RDP onto a machine unless I use the IP address.
I'm not going to worry about it though since I had this issue before in the past. I cannot remember what I did to get it so machine names are usable. I suspect that what I did was undone by the last fast ring update. I'm not really going to call this a problem anymore since I have had other settings get reset by the fast ring updates.
- RedBetaIron ContributorI got Build 19587 installed....this seems to be a continuation of the winre.wim issues that started with builds back in December.
- RedBetaIron Contributor
So this build has a new issue....
Notice: We had a problem with this update....run Fix issues
I run fix issues (select button).....it runs.
"We couldn't update the system reserved partition"
"This PC can't run windows 10"
Other than this being a business class laptop....it has been running the windows 10 insider program for years.
???
RedBeta wrote:So this build has a new issue....
Notice: We had a problem with this update....run Fix issues
I run fix issues (select button).....it runs.
"We couldn't update the system reserved partition"
"This PC can't run windows 10"
Other than this being a business class laptop....it has been running the windows 10 insider program for years.
???
do you get that error when downloading or during install? never seen it happen to me
- RedBetaIron Contributor
I had never seen it before either....it popped up during the beginning of the download.
I was one of the ones that had builds stuck at 62% at the beginning of the year. It was posted all over feedback hub.
I resolved the (stuck) issue after i found reagentc /info showed that winre.wim was disabled and in fact missing.
Since the machine is essentially static except for insider build installs / updates.....the source of the problem must have been an update in December.
I don't know if there is a new image that was larger or what....but my system/recovery partitions are over sized and there is unallocated space on Both Disks as well.