Mar 18 2020 10:38 AM
Hello Windows Insiders, today we’re releasing Windows 10 Insider Preview Build 19587 to Windows Insiders in the Fast ring.
Mar 19 2020 08:05 AM
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.
???
Mar 19 2020 01:49 PM
Mar 19 2020 03:28 PM
Mar 19 2020 03:36 PM
@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
Mar 19 2020 04:00 PM
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.
Mar 20 2020 02:45 AM
Mar 20 2020 08:45 AM
Actually this install is not that old....it takes me longer than 3 hours (as I still have not installed all my programs from the last time).
At least I have an error message to track down....the stuck at 62% had NO ERROR in any logs what so ever. The errors most often reported on the feedback hub is simply a built in timeout of the installer or the one caused by a shutdown when the installer is running.
For me it is not a big deal....but the issue started with a 20H1 build. Hopefully they have addressed this....since pushing out a build to people with partitions from upgraded (win8, win7) could be an issue. Expecting them to do a clean install won't work.
I find the feedback hub not very useful.....a couple of years ago a new build rushed through even though numerous reports of data loss on update. Sure enough the general release saw some data loss.
I have a winre.wim now installed in the recovery partition .... when I resolved the issue about not getting updates I only activated (pointed) to a winre.wim on the active partition which worked, but was not a full solution.
Mar 20 2020 10:49 AM
Mar 21 2020 11:39 PM - edited Mar 22 2020 02:20 PM
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.
Mar 22 2020 01:25 AM
Mar 22 2020 01:39 AM - edited Mar 22 2020 01:43 AM
@HotCakeX
L2TP/IPsec; it's the Cisco Meraki VPN "client" (which I really do not like because it is very sensitive to Windows updates and does other weird things). Also, it tends to misbehave through the Windows 10 UI so I have to fall back on Rasphone.
Mar 22 2020 01:55 PM
Mar 22 2020 02:14 PM
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.
Mar 22 2020 02:18 PM
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
Mar 22 2020 02:19 PM
Mar 22 2020 03:14 PM
@StephenWhiteD3G wrote:
@HotCakeX
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.
Well hope you remember what you have to do to fix it soon :)
Mar 22 2020 03:16 PM
@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."
Mar 22 2020 03:33 PM
I had no mentioned it...but build 19587 is requiring me to use IP address vs name for several things.
I use WSD so the network file servers show up under "network" just fine....but I can't get to them by clicking on them (need to use IP). I have the same for RDP.....need to use IP.
I did go through and check name resolution and it is working fine from a command prompt...my understanding is that name resolution and connecting are not hard linked, so it is possible for resolution to be ignored during connection.
In my case there was nothing done on the windows machine for WSD.....those changes where all done on the server and automagically worked on windows.
Mar 22 2020 03:47 PM
This is what I did to get past the 62% after months of broken updates...
In order to locate the Winre.wim file, you can search the file on your computer. From an elevated Command Prompt, type the following command to search for the Winre.wim file on C: drive:
dir /a /s c:\winre.wim
When you find the Winre.wim file and it is vaild, you can type command “reagentc /setreimage /path [path of Winre.wim]”. For example, “Reagentc /setreimage /path C:\Recovery\WindowsRE”
Then reboot enough to get WU to restart the download / install of the new build.
I have no proof...but I believe that the winre.wim on the recovery partition was corrupted by a past build. I tried many things during Jan and Feb to get the builds to install....and this is the only thing that worked.