Windows 10: Announcing Windows 10 Insider Preview Build 14936 for PC and Mobile

Edge finally opened after about five crashes.
The error in Reliability History was Browser_Broker:
Code: Description Faulting Application Path: C:\Windows\System32\browser_broker.exe Problem signature Problem Event Name: BEX64 Application Name: browser_broker.exe Application Version: 11.0.14936.1000 Application Timestamp: 57e61be1 Fault Module Name: browserbroker.dll Fault Module Version: 11.0.14936.1000 Fault Module Timestamp: 57e61b44 Exception Offset: 0000000000001b98 Exception Code: c0000409 Exception Data: 0000000000000007 OS Version: 10.0.14936.2.0.0.256.48 Locale ID: 1033 Additional Information 1: 6471 Additional Information 2: 6471d20fdf3fb5f1af0899cbe15f430b Additional Information 3: 533c Additional Information 4: 533c14f56adf174f50f6728c6d16e788 Extra information about the problem Bucket ID: b19de08447dece459c53a6affe7e41f7 (116244810725) [/quote]

 

See post #20

 

@dencal, I got Edge working by just repeatedly trying. MBAE is still installed. If I have to choose between Edge and MBAE, Edge, goes, MBAE stays, as I have other browsers*Wink

 

Finally got the chance to install 14936. It seems like trying on the 2nd day works for me. Only problem is that somehow my D: (data drive) got the recycle bin corrupted message after the install was done. Had this happen before, 3-4 builds ago, but this is a brand new replacement WD HDD. Only thing I can think of now is to change the sata cable out in a new sata port?? and see if it repeats.

 

Downloaded on laptop. Install failed. Reloaded download. Second attempt failed, also. Someone said NVidia driver was a problem. Wonder if that is the problem with this attempted /aborted upgrade. This has never been a problem and this device usually updates before my desktop WITHOUT A FLAW. Will now attempt to do clean install.

 

This has happened to me on a couple of builds along the way. Restart after the download, some stuff happens, it gives some error message I can't recall, reboots, and immediately starts downloading the whole thing from scratch. Sometimes, the second go-round works fine, sometimes not.

So.. the first thing I do, after the download and before pulling the trigger on the restart, is copy install.esd to another partition. If the install fails, I just make an iso, mount it, and launch setup.exe. I have a slowish Internet connection, and I can't be waiting for another download.

Incidentally, the update to 14931 worked just fine. I'm just about to start the update to 14936 - we'll see how it goes!

 

Good Luck with 14936! I am now installing from iso on my laptop.

 

Install from ISO also failed. Guess I won't be getting this build on the laptop. Have been successfully installing every build since January of 2015. Never had problems before on laptop.

 

Well, this time it worked as designed. Seems an awful lot like 14931, oddly enough *Party Sorry your iso install didn't work. So many different hardware permutations out there - it's a wonder things work as well as they do...

 

Happy for your success. I have removed nvidia driver and nvidia update program and am trying installing again. Windows seems to like to download video drivers and it is queuing nvidia and 14936 so we'll see what happens.

 

It's now unable to map the network's drives, but previous mapped drives remain working unchanged. Network computers are all disappeared except Media Devices and Infrustructures. Set all to private won't work for me.

Edit: It's unclear if this is a permanent change from MS or not!

Edit 2: You can still manually enter drive IDs to connect though!

 

After multiple attempts including clean install, I have given up with install of 14936 build. It installed on my desktop but not laptop. All other builds since January 2015 have installed without problems. Will wait for next build and try again.

 

Easy workaround to add mapped shares:

In PowerShell, enter the following command:

Code: New-PSDrive -Name X -PSPriver FileSystem -Root \\COMPUTER\ShareName -Credential USERNAME_TO_ACCESS_SHARE -Persist[/quote]




As name, replace the X in above example with drive letter you want to assign to share. The -Persist switch keeps the drive mapped even after restart.

Enter password for share credentials:




That's it.

 

As name, replace the X in above example with drive letter you want to assign to share. The -Persist switch keeps the drive mapped even after restart.

Enter password for share credentials:




That's it.[/quote] The Honcho PowerShell Geek strikes again!*Smile

 

Attachment 103791

As name, replace the X in above example with drive letter you want to assign to share. The -Persist switch keeps the drive mapped even after restart.

Enter password for share credentials:
Attachment 103793

That's it.[/quote] Thanks for the workaround Kari. *Wink