New
#60
Glad I am not the only one who isn't getting the most recent Fast ring build....I will continue to be patient here in CA, USA
Glad I am not the only one who isn't getting the most recent Fast ring build....I will continue to be patient here in CA, USA
Ok. So got the above error. Disabled aVast. Removed Stardock programs same error message Windows 10 Insider Preview 14915 - Error 0x800703ed This happens always at starting install 25%
1) Created a 14915 ISO from the install.esd from a successful VM install.
2) Will do a clean install
3) Will only install Hyper-V and Ubuntu Bash for Windows.
4) Install Remote Desktop Connection
5) Install Aoemi Backupper 3.5 and make a backup image. Then - most importantly Install openSUSE Leap 42.2 Beta 1 and enjoy dual booting.
The following build announcement - after more than 3 weeks of work is the single poorest changelog product I have ever seen.
------------------------------------------
Improvements and fixes for PC
We fixed the issue with being unable to use the power button on the Start menu.
We fixed the issue causing Cortana’s text to speech capabilities to not work. Cortana should be able to read text messages out loud for you, tell jokes, sing, or give verbal prompts as expected.
We fixed the issue causing the Settings app to crash on certain editions of Windows 10 when navigating to different settings pages due to a missing .dll file.
We made a number of improvements to translations, including fixing an issue in Windows Update where it would say “your phone is up to date” in French when confirming that your PC was up to date.
Changing functionality via Settings > Update & security > Windows Insider Program such as your ring settings should now work again on this build. For more information – see this forum post.
We fixed a compatibility issue from a recent platform change that causes apps such as Yahoo Mail, Trivia Crack, Google and the Skype Translator Preview app to crash.
We fixed an issue resulting in some Insiders experiencing a delay in Mail notification toasts appearing.
We fixed an issue where the “Open with” dialog’s “Look for another app on this PC” link wasn’t working if the dialog appeared after using the “Run” dialog to open a file with an unassociated file type.
We have updated the Connect flyout so that the clickable area for each device listed now spans across the full width of the flyout.
We fixed an issue where if a Chinese Input Method Editor is active it could result in logging in to not succeed after device goes into and is woken up from Connected Standby.
We fixed an issue where for certain websites in Microsoft Edge, using CTRL + A to select all text and then copying it and trying to paste it into Notepad wouldn’t paste anything.
We fixed an issue where importing favorites into Microsoft Edge from Internet Explorer would fail if the Favorites folder had been redirected to another folder, for example “C:\Users\<user>\Documents\Favorites”.
Known issues for PC
Adobe Acrobat Reader crashes when you try to launch it.
You may experience a black screen when signing out and switching to another user account and will be unable to log in to that account. A reboot of your PC should allow you to log in to that account.
Bash may not work after upgrading to this build. To get it working again, go to “Turn Windows features on or off”, scroll down and check “Windows Subsystem for Linux (beta)” and click ok. After a reboot, Bash should work again.
The Settings app may crash when going to Settings > Personalization.
-----------------------------------------------------------------
On the bright side I will install Windows 10 Microsoft Mail as its the best email program I've come across (for my needs) on Windows or Linux (beats T bird hands down)
Last edited by martyfelker; 31 Aug 2016 at 22:12.
This one computer build keeps freezing when I log out. I don't think it's the new update. I will fix it.
That's all good to know and I usually get new insider builds right about now on day one if it's going to be day one but not so far today .
I'm out here on the other left coast as well but my 14905 build is stuck on the slow ring Insider new build WU branch per the known issue . Were you on the slow ring or fast ring Windows Insider WU branch ?
Sent from 14905 my 14915 update is lost somewhere or locked out and hasn't come in to my $WINDIWS.~BT folder or WU
Last edited by electronuser; 01 Sep 2016 at 01:41.
Well, at least I am not alone! Now, is it just some of us or all of us?
More feedback, please, folks.
I am not very pleased at this deja vu moment. Looked back on on an earlier thread with 284 posts on a similar problem!
It just seems to me that NetBIOS is not functioning.
Edit:- can now see all comps via WSD but not NAS and networked printer that need NetBIOS.
FWIW the last time windows Insider WU delivery branch was stuck on slow in 04/16 these registry changes fixed it temporarily but when you open WU to check for a new build and close WU they go back to what they were and you have change them again until you open and close WU again if your new build has not shown up . All this drama worked for some of us until the fix was in the next build these changes let us roll in YMMV.
ofc this is all Windows beta drama after all but when it works, it beats rolling back or waiting for a slow ring flight to get a new build . .
last time it was a 5 hour interval to get my new build after these changes after never ever ever being four days late here before this reg hack was figured out and used by some of us at Windows Insiders forums .
Hopefully it will work on 14905 stuck on the slow ring Insiders WU branch but I will see if I don't find an alternative or just get the luck of the draw but as I understand it at the moment they are only flighting 14915 on the fast ring now after doing both rings last night briefly .
If anybody gets 14915 on the slow ring branch this PM or later pls .let us know .
FWIW I usually get my new Insider builds since they started flighting them in WU the first day or evening or overnight from there or next am .
The correct REG_DWORD # settings and REG_SZ word that worked for us are highlighted except Ringld REG_DWORD # that should be (1) also .
ofc the registry directory tree path for this hack is at the bottom of the image ☺
OFC in this crowd I expect everyone knows how to do all this and export a registry to a named folder somewhere before making any changes and note them down as well .
Sent from 14905 my 14915 update is lost somewhere or locked out and hasn't come in to my $WINDIWS.~BT folder or WU
Last edited by electronuser; 01 Sep 2016 at 01:41.
Right thats my understanding after they allegedly flighted both rings briefly last evening but I may have a fix posted here in the registry image post # 69 , thanks for confirming that you were presumably on the fast ring branch for me and us ,that's what I was assuming and wanted to know . I never got a fast ring new biuld flight stuck on the slow ring and don't expect to now .