Announcing Windows 10 Insider Preview Build 14251 Insider

Originally Posted by badrobot

So, some people are still using "Insider Builds" as their main OS?

It's not advisable to replace your main OS with preview builds. But if you have backup plans like images, it's not a bad idea to do so.

Bunny J

I do and I know that I'm running a risk but I'm all set to re-install everything and get up and going in a few hours at most. It might take about 2 hours to install 10240 and upgrade to the latest build then about 2 more hours to reinstall the rest of my main tools. Not really that hard,

badrobot said:

Yup. I know it isn't hard. Just time consuming. But if you have a spare SATA port, it's better to play around with the preview on a separate playground, away from the main flawless 10586. :) But if you accept all the risk, that means you can't complain right? Just send a feedback and that's what we, Insiders, do.

Right , I use the Insider test builds on this dual boot NTFS partition with activated 10586 on the other side and backed up on another NTFS HDD altogether and updated frequently .

I save anything important to 10586 stable and or or external media and generally use a standard user account on the web on all my PC's .

You never know how any given test build will be and any $$$ transactions are outside of the test builds unless it's something inexpensive with Pay Pal .

I've been test driving Insider test builds on this NTFS partition for just about a year to the day now .

I have 2 other desktops and an HP Elite book running 10586 also :)

Wynona said:

I kinda am, but on the other partition, I have the "RTM", so if something goes terribly wrong with an Insider build, I can drop back to it. I kind of enjoy using the Insider builds as a main OS without having to worry about trashing my system. Errr, ummm, until this morning!

And that's exactly what happened! I am sooooooooo glad I didn't install the beta of Malwarebytes Anti-Malware on the RTM partition because . . .

I was notified that a new Insider build of Office 365 2016 was available, and since I was on the Insider partition, I went for it. Yep, you guessed it! MB Anti-Malware pegged O365 as malware! It quarantined Click2Run and a couple of other update files of Office. Nothing I could do would make MB release its hold. I could understand if it were some minor program, but Microsoft Office?

So, now I have to do a clean install of the new build. Sheesh, am I glad I didn't run that crapola on my RTM partition! I wouldn't worry about it so much if I hadn't installed a number of my everyday programs and now have to reinstall those too. So, guess I'm gonna have to even make backups of my Beta partition too.

Wynona, make it a habit to create a restore point before installing anything you are not sure about. That is the simplest trick you can do to fix the problem you had with MB... a 5 minute system restore.

Installed and running ok on backup computer.
Tried to install on UEFI Sabertooth and it downloads correctly but when it reboots it cannot find a boot device.
is there a workaround for this?
Brian

Edwin said:

I find it quite handy to have 'the two' running side by side.
Just last night, I made, what I thought, was a harmless shellstyle mod. and ended up 'nuking' Explorer altogether;
but I was able to 'reach in' from the other Build and re-merge the backup dll!
Not an encouraged method of doing things, by any means, but it worked!

Well, I have both the RTM and the Insider version running side by side on the same machine (each are separately licensed) but I don't have it on dual boot. In fact, the 2 don't communicate with each other. I have the RTM on GPT disk (on M.2 SSD) and the Insider Preview on MBR (on regular SSD). That way, I can upgrade the Insider version anytime without worrying about messing up the boot manager of the RTM. I just select the boot drive on startup. But both OSes share the same data drive so I can access my active documents whichever OS I chose to boot up.

Kodi said:

Installed and running ok on backup computer.
Tried to install on UEFI Sabertooth and it downloads correctly but when it reboots it cannot find a boot device.
is there a workaround for this?
Brian

In BIOS, check if the boot priority is set to "Windows Boot Manager".

badrobot said:

Wynona, make it a habit to create a restore point before installing anything you are not sure about. That is the simplest trick you can do to fix the problem you had with MB... a 5 minute system restore.

Agreed.

linw said:

Wyn, was that the paid for resident version of MBAM?

No, the beta they just released a couple or so weeks ago. Malwarebytes Anti-Malware. Which is gone from my computer, never to return!