Announcing Windows 10 Insider Preview Build 14385 for PC and Mobile Insider

As many Stable Release users might want to test Insider builds before deciding if opting in is something for them, I will quote myself from TF Video thread here (read the tip at bottom of the quote!):

Kari said:

Tweet

— Twitter API (@user) View on Twitter

New video: Windows 10 - Test & Try with No Risk, No Installation needed (for Win8 users)

Video is meant to show Windows 8 / 8.1 users how to test Windows 10 risk free on their real physical hardware, without any virtualization or need to install Windows 10, using a pre-installed 90 day trial version of Windows 10 on a virtual hard disk in dual / native boot.

Very simple procedure, totally free for 90 days, lets you test & try Windows 10 in dual native VHD boot before upgrading. Time needed for the whole process (not counting download & ZIP extraction time) = one minute :)



Full video description and tutorial at EightForums.com: Windows 10 - Test Try with No Risk, No Install

This is basically the same than tut & video posted earlier for Windows 7 users, however the process is different enough in Windows 8 to justify its own tut & video.

Extra credits and kudos to our resident GFX guru @kado897 for title background and Windows 8 wallpaper.

   Tip

Are you Windows 10 Stable Release user, wanting to test latest Insider Preview builds before deciding if opting in is something for you?

Although this video is made for Windows 8 / 8.1, the process of using pre-installed Windows 10 Insider Preview on a VHD in native dual boot is exactly the same in Windows 10. This video and tutorial apply as they are to Windows 10, letting you test Insider build on your real hardware without installing it, with no risk.

After using this build for just over a day I think the prospect is looking very good for the Anniversary release. Finding little to dislike in this release :)

Just activated Windows 10 Build 14385 in a VMware WS VM using the Activation Troublewhooter. No problems at all.

fjk61011 said:

OK, I cleaned installed 14366 from the MS ISO. Same behaviour. Endless downloads of the graphics driver. Makes me think the problem is at MS end.

I'll try Kari's Tutorial.

I would have recommended going with a newer build for a clean install at this as far as Insider build or go for the update TH2 which would see the 10585.318 or something like that at this time until the August 2 Redstone 1 anniversary update arrives. Also besides the check box for keeping all files you can uncheck the get updates box and go into the Settings Update & Security>Advanced options to check off the Defer updates box there to prevent any continuing problem.

Going direct to the manufacturer's own update site and downloading the correct full update available would still be a recommendation however to insure the correct drivers are what are going on as well as being on fully. I run into this type of problem with two older expansion cards one being a discontinued tv tuner card still in use where I have to grab the 8.1 x64 drivers and app for a similar but for a different PCI Express not PCI model card.

The web updater option seen with the Creative X-FI XTreme Audio also 8.1 gets the Support 1.2 and then puts on the 1.5 updated for 10 driver set not found at the support site as the alternate route for the sound card. Yet I am still able to keep older wares running at this time by innovating things a bit.

martyfelker said:

Just activated Windows 10 Build 14385 in a VMware WS VM using the Activation Troublewhooter. No problems at all.

Why did you need the trouble shooter - were you transferring digital licence from another VM?

Night Hawk said:

I would have recommended going with a newer build for a clean install at this as far as Insider build or go for the update TH2 which would see the 10585.318 or something like that at this time until the August 2 Redstone 1 anniversary update arrives. Also besides the check box for keeping all files you can uncheck the get updates box and go into the Settings Update & Security>Advanced options to check off the Defer updates box there to prevent any continuing problem.

Going direct to the manufacturer's own update site and downloading the correct full update available would still be a recommendation however to insure the correct drivers are what are going on as well as being on fully. I run into this type of problem with two older expansion cards one being a discontinued tv tuner card still in use where I have to grab the 8.1 x64 drivers and app for a similar but for a different PCI Express not PCI model card.

The web updater option seen with the Creative X-FI XTreme Audio also 8.1 gets the Support 1.2 and then puts on the 1.5 updated for 10 driver set not found at the support site as the alternate route for the sound card. Yet I am still able to keep older wares running at this time by innovating things a bit.

I had clean installed with the MS ISO Build 14371. After the first reboot I got a warning screen that the BIOs/UEFI was corrupt. After getting back into the BIOS I loaded the default management? Keys. This allowed the install to continue. I tried again and got the same behaviour. Now clean installed, I let 14385 percolate, or whatever it does now, and after a few hours it picked up 14385. This had the endless loop downloading the Intel Graphics 4600 update.

Next experiment, clean install MS ISO 14366, which before didn't have the endless loop. But this time it did which makes me think the problem is at MS end. I used Kari's tutorial to stop the endless loop. Now waiting for 14385 to appear.

I'm "up to date" at 12:40 PM Central Time.

And while I go out to get a water hose repair kit and DentaBones for Gracie, it will most likely drop!

fjk61011 said:

I had clean installed with the MS ISO Build 14371. After the first reboot I got a warning screen that the BIOs/UEFI was corrupt. After getting back into the BIOS I loaded the default management? Keys. This allowed the install to continue. I tried again and got the same behaviour. Now clean installed, I let 14385 percolate, or whatever it does now, and after a few hours it picked up 14385. This had the endless loop downloading the Intel Graphics 4600 update.

Next experiment, clean install MS ISO 14366, which before didn't have the endless loop. But this time it did which makes me think the problem is at MS end. I used Kari's tutorial to stop the endless loop. Now waiting for 14385 to appear.

What I saw done with a problematic install on a VM however was revert back even further to the latest MC Tool without the actual however just ISO for the TH2 with the latest updates and allowed that to update itself to the latest Insider build at the time which was likely the 328 following some problems witth 295 and 316 builds I had run into.

At this you would likely see the 361 or 366 as the first Insider build when enabling the option following a clean install and then subsequently moving onto the next newer over time. With the direct download of the last latest build which now would be the 379 or 383 skipping the updates option by leaving that box unchecked at either upgrade by update or clean install should allow you to manually check for things at the support sites without running into the looping issue.

Actually I did download the MS tool indicated in the guide Kari pointed to but as of yet have actually had any occasion to use it. Disabling the WU entirely by going into Settings>Update & Security>Advanced options there until getting the essential hardware updates on you find at the support sites being sure to keep those backed up in a safe place as well once attained will then and should later allow you to receive the normal MS updates without any further issues.

This was what I was trying to explain before if you are still finding the same situation of looping. Basically you turn the Windows update function off long enough to manually track down what you need to get past the one or more items hanging on you before returning to the normally functions. If one thing doesn't work you simply try another to see if you get results.:)

New build coming up soon possibly.

Tweet

— Twitter API (@user) View on Twitter