Windows 10: Announcing Windows 10 Insider Preview Build 14257

FWIW Favorite browsers in this order here are :

1.Chrome

2. Fire Fox

3. IE 11

4. Edge

OTOH ...You can stream Netflix 1080p in IE 11 or Edge, not sure about F/F and definitely not Chrome

note : aside from 1080p Netflix browsers 3 and for 4 are mostly only good for downloading a better browser like 1 and 2 *Smile

 

Here is my experience using Kari's(?) ESD to ISO tool.

1. Made an ISO using the .wim method, 1st option on tool.

2. Tried to use DISKPART with the 14257 DVD but their was no option to get a Command Prompt.

3. Used 11102 to use DISKPART to clean my 1st drive.

4. Now the interesting bit: I booted from the 14257 DVD. A "DOS" window came up and said something about source not being found but then continued to install.

5. During one of the restarts a "DOS" window came up and said something about source not being found but then continued to install.

6. Install completed and 14275 seems to be working fine.

Should I post this in a new thread?

 

Yeah, but we both have subscriptions to Office 365 2016 for business. In my case, my subscription is free until November of 2016 and will cover five computers and five tablets. Still, it's good to have the free ones that will play nicely together. I don't know what Joanne has, since there are multiple subscription types to Office.

Skype for Business and OneDrive for Business come with Office for Business. Both have more features than I understand, thus, the reasoning behind wanting a user guide for them. I get a whole terabyte of space with Office 365 (home or business), so I really don't need any other storage. It's also pretty fast.

Reasoning as above for not using anything other than what I have.

 

Yeppers! Although it is getting a bit better.

 

Reverse 1. and 2. and you have my faves. *Smile

 

not done a clean on mine and system restore was switched off so had to put it on again

 

It didn't on mine either, but maybe because System Restore wasn't turned on before 14257 install. I prefer to rely on fresh Macrium Reflect backups. System Restore hasn't always worked properly for me.

 

mine was turned on before latest update
the last few updates it had to be turned on after update
don't have important things on it so will do a clean install if it goes pear shaped

 

Got it installed finally. Surprised how quickly this build arrived to me. Usually takes 2-3 days to arrive on my pc. Yeah!

 

Mine is almost there, waiting to find out if it tore up my VM Mint 17.3?

 

I have to stick with Chrome not just because it's my favorite but because it's the only one that works with my Qnap NAS.

 

Just got it successfully, easier than the last build.

 

Build 14257...This is the second consecutive build that will not install on my machine...14251 wouldn't either...I haven't had this much trouble with installing Windows builds since I signed into the program in 10/1/2014--the pre-Win10 launch builds never gave me as much trouble. I reported this problem a week back and yet it isn't mentioned anywhere in the list of known or fixed bugs in 14257.

My system @ home:
MSI 970 Gaming motherboard, latest bios, M.4
AMD FX-8320e @ stock speeds
8GBs (2x4) running @ stock 2133MHz
Samsung SSD 850 EVO 250GB (boot)
2 x ST3500418AS HDs
2 x WDC WD10EZEX HDs
AMD R9 380 4GB GPU running the Crimson 16.1.1's

Last successful build 11099



When doing the internal "flight" install through WU, everything is fine through the "copy files" portion of the install--it hits 100% and the system auto reboots to continue the install...and then *WHAM* suddenly I have a blue screen failure INACCESSIBLE_BOOT_DEVICE...upon reboot, even if I hit F11 and manually select the boot drive--it does not matter, the system fails to boot and I am restored to my last fully working build 11099...! Thank goodness the "restoring previous build" function has worked perfectly each time.

My SSD drive is fine of course and the "previous build" I have is located there as well--so the error is clearly a build problem & bug and it would be NICE if it was acknowledged somewhere. The only time I have ever seen this error under normal operating conditions is when the system tries to boot with the IDE driver installed instead of the AHCI driver--the SSD *requires* the AHCI driver and will not function with the IDE driver. All the Win10 builds I've tested since 10/2014--all of them--successfully carried the AHCI settings over to the next build. (Except 14251 and 14257.)

I ran across one person in Feedback who had the same error I did, INACCESSIBLE_BOOT_DEVICE, and he reported that disconnecting all the drives in his system except for his c:\ boot drive got him past the error and allowed him to install. Didn't work for me.

Ideas, suggestions, anyone?

 

Updated to new latest build and all is well *Smile

 

anyone in California got this update? Please advise!
check for last 16 hours and it's not appears yet!