Announcing Windows 10 Insider Preview Build 14971 for PC Insider
-
The only clean install I did was the first one when I started with 10 Insider Preview. I've had to revert to the previous build with a Macrium backup a number of times, but clean installs would be entirely too much work with all the programs and custom settings I have on that PC.
I just wanted to see if some problems would go away with clean install but they didn't or got solved another way. Didn't install too many programs in it anyway. MR backup returned me where a I was before, programs and everything.
-
-
Getting the ESD file and creating install media is not only for clean install. It's main purpose is of course to be there in case something happens; it allows repair install, and if nothing else helps the clean install.
You don't use life belt on a boat only if you are sure you will wreck the boat, or seatbelt in a car only when you are sure you will have an accident. In the same way not creating Windows install media because you don't plan to clean install is in my opinion not very clever.
As it has lately been here, I feel it necessary to add this: The above is my personal opinion. It is not meant to be taken as a recommendation, not even a suggestion; each user may of course do as he / she prefers. This post is not personally targeting one or more fellow members. The intention of this post is not to downplay any other posts from any other members, nor am I trying to imply that I know this better than some other users. I am simply stating my honest opinion fully accepting that your opinion might be totally different.
Kari
I agree. IMHO it's always best to be safe then sorry. I try to save all my ESD files and make a ISO just in case I need to do a clean install or as you mentioned a repair install. A repair install has helped me more than once. There have been a few times I forgot to save first and when I restarted the install.esd was gone. Luckily I didn't have any problems were I need it.
-
There's only been a couple of times I used the install.esd to do a clean install. I feel that by testing upgrade installs instead of clean installs I am doing my part to help MS make upgrades as painless as possible when they release builds to the general public.
Lin, I always do the update, and then if there are really bad problems, I may do a clean install. I did a clean install on Build 14971 the other day because I must have caught a drive-by virus. I was looking for a particular type of app and stopped by some sites to research. My bad, but since this is a non-production machine, a clean install isn't all that tough.
-
Lin, I always do the update, and then if there are really bad problems, I may do a clean install. I did a clean install on Build 14971 the other day because I must have caught a drive-by virus. I was looking for a particular type of app and stopped by some sites to research. My bad, but since this is a non-production machine, a clean install isn't all that tough.
I was reading about all the problems you were having. I would have done a clean install also. Like you said sometimes you need strong medicine. :)
-
-
I hope that everyone who celebrates it had a wonderful Thanksgiving--my gut doth burst with ham & turkey & sweet-potato souffle... Enough for an entire *year*... (I feel like a slug this morning!)
Wanted to ask, though, if anyone using a Firefox browser has noticed really high instability with 14971...? I use a fully updated Firefox DE x64, and since 14971 was installed it's crashing like crazy--everywhere--it will probably crash while I'm typing this query, in fact. Even after I reset it through preferences--it's still crashing. Very unusual--has been rock-solid in every build until now....I have no other problems in the build to report--however, many people in this thread have reported problems, so it's surely possible that something has regressed under the hood in this build...comments?
-
I hope that everyone who celebrates it had a wonderful Thanksgiving--my gut doth burst with ham & turkey & sweet-potato souffle...
Enough for an entire *year*... (I feel like a slug this morning!)
Wanted to ask, though, if anyone using a Firefox browser has noticed really high instability with 14971...? I use a fully updated Firefox DE x64, and since 14971 was installed it's crashing like crazy--everywhere--it will probably crash while I'm typing this query, in fact. Even after I reset it through preferences--it's still crashing. Very unusual--has been rock-solid in every build until now....I have no other problems in the build to report--however, many people in this thread have reported problems, so it's surely possible that something has regressed under the hood in this build...comments?
Yes, I get a lot of "Not responding" at the top. Most of the time it lasts a second or two. Just like if it was waiting for something to happen. During that time scrolling stops.
-
FWIW. I am on x32 and has been stable for me.
-
Yes, I get a lot of "Not responding" at the top. Most of the time it lasts a second or two. Just like if it was waiting for something to happen. During that time scrolling stops.
Thanks for the replies, guys...strange...after I opened up Edge yesterday, then minimized it, then ran FF DE x64...I stopped having problems. Today, FF has updated and I'm running it fine without running Edge at all. Very odd!
-
Build 14965 from Microsoft awaiting update 10 194971. VM under Build 14971. Virtualbox latest bombs btw.
Udated to 14971 no incident
Last edited by martyfelker; 27 Nov 2016 at 09:38.
-
-
Virtualbox 5.1.10 is OK. Just had to install it as Administrator. Thanks to Socrates at the Virtualbox forums.