Announcing Windows 10 Insider Preview Build 10547 for PC Insider
-
This build is definitely a bit flaky, had a BSOD while updating, then it wouldn't boot, then when it did boot lost wireless connection. When it started all working again a message popped up to say that updates wouldn't install, and that it would have to install them separately, it started to install them, then said it couldn't install them again.
Anyway it seems to be running ok at the moment, just hope the next updates fixes things.
-
-
Given the various complaints it seems like I need to keep my VM's network disconnected (until the next build is released).
-
I'm happy with this build so far. Haven't had any issues.
-
![]()
This build is definitely a bit flaky, had a BSOD while updating, then it wouldn't boot, then when it did boot lost wireless connection. When it started all working again a message popped up to say that updates wouldn't install, and that it would have to install them separately, it started to install them, then said it couldn't install them again.
Anyway it seems to be running ok at the moment, just hope the next updates fixes things.
EDIT :
No issues with three Window 7 x64pro > Win 10 pro RTM upgrades here or the latest test build 10547 in place update on the dual boot NTFS partition on this box other than the known isssues on the earlier builds and the usual mail client and Groove music UI app instabilities acrooss the board and an *occasional* applicatin hang now and then .
Hopefuklly the service pack or whatever they call it now later on will tighten things up a litttle across the board .
I'm typing this in test build 10547 ( the daily driver of choice here . ) I've found wireless connection is much faster and easier on Win 10 across the board here especually when set to automatic even on the HP 8470P Elitebook .
ofc . I install all my own sound,video and wireless drivers and dont let Windows choose them sometimes Windows gets those all wrong it always has now and then well before Windows 10 .
. YMMV with all this ofc ☻☻
Last edited by blutos cousin; 23 Sep 2015 at 23:07.
-
-
![]()
No issues with three Window 7 x64pro upgrades to Windows 10 RTM pro here (2 destops and one Elitebook ) or in place updates for 4 or more or of the most recent test builds on *the Insiders test build* dual boot NTFS partition on this box .
I'm typing this in test build 10547 ( the daily driver of choice here . ) I've found wireless connection is much faster and easier on Win 10 acrooss the board here especually when set to automatic even on the HP 8470P Elitebook .
ofc . I install all my own sound,video and wireless drivers and dont let Windows choose them sometimes Windows gets those all wrong it always has now and then well before Windows 10 .
I keep the latest known good chip set and controller drivers & firmaware & HDWE drivers as well Bois in reserve on external media for each box also just in case Windows blows that or they need to be re installed also ......seen it happen . ☻
One thing I did was a totally clean install from an ISO DVD on the HP elitebook *after an in place upgrade /activation* and and I used updated recent clean 7 x64 installs for the in place upgrades on the other two ......but with all the files and media in place no issues and presumably not a lot of accummulated windows 7 garbage . YMMV with all this ofc ☻☻
Ive had no problems with RTM either, I've got it on 3 computers and a Mac, but as soon as 1057 started coming down I've had problems, it's only this computer on the fast build now, it's just for testing, I don't want to clean install it, I want to test it, and it's not good this time.
On the Mac I had to put special drivers to get a few things working, but I'm not interested doing that on this machine, this is purely for testing, and like I said, it's not doing too well this time around.
-
![]()
Ive had no problems with RTM either, I've got it on 3 computers and a Mac, but as soon as 1057 started coming down I've had problems, it's only this computer on the fast build now, it's just for testing, I don't want to clean install it, I want to test it, and it's not good this time.
On the Mac I had to put special drivers to get a few things working, but I'm not interested doing that on this machine, this is purely for testing, and like I said, it's not doing too well this time around.
I had a lot of trouble with maybe 10261 or 10266 or something like that it was a PITA and thern some ( it was the one w/o a working start menu or task bar search or working mail client UI app all on the same build ) ☻ You never know on these test builds on any given configuration so I can see where it may not work for everone on any given test build .
10029 hosed itself here beyond repair with an automatic sound card driver update after 3 days in . I had to delete it from the NTFS partition and re install it from an ISO and install the drivers I had before the update .
-
![]()
Ive had no problems with RTM either, I've got it on 3 computers and a Mac, but as soon as 1057 started coming down I've had problems, it's only this computer on the fast build now, it's just for testing, I don't want to clean install it, I want to test it, and it's not good this time.
On the Mac I had to put special drivers to get a few things working, but I'm not interested doing that on this machine, this is purely for testing, and like I said, it's not doing too well this time around.
BillyBob, testing isn't only using what you've been given . . . it's also a clean install after you've encountered all the bugs. Then comparing the clean install against what you found in the update/upgrade. Checking to see if you still have the bugs or if they've hit the road. :)
I do find it harder and harder to force myself to do a clean install because I'm using the computer more and more for day to day stuff. As well, I've installed way too many programs! Reinstalling those is going to give me the heebie jeebies!
-
BillyBob, testing isn't only using what you've been given . . . it's also a clean install after you've encountered all the bugs. Then comparing the clean install against what you found in the update/upgrade. Checking to see if you still have the bugs or if they've hit the road. :)
I do find it harder and harder to force myself to do a clean install because I'm using the computer more and more for day to day stuff. As well, I've installed way too many programs! Reinstalling those is going to give me the heebie jeebies!
Yes I know but I just want to see how Microsoft is going with these upgrades, I've done a couple of clean installs, I just want to see how far I can go without another clean install. This is not my main computer so it doesn't matter unless it just become a mess, at the moment it's limping but not defeated.
This is really the first time I've had a problem in quite some time, going back to 1030 or whatever it was that wrecked my SSD.
-
![]()
Originally Posted by Wynona 
BillyBob, testing isn't only using what you've been given . . . it's also a clean install after you've encountered all the bugs. Then comparing the clean install against what you found in the update/upgrade. Checking to see if you still have the bugs or if they've hit the road. :)
I do find it harder and harder to force myself to do a clean install because I'm using the computer more and more for day to day stuff. As well, I've installed way too many programs! Reinstalling those is going to give me the heebie jeebies!
^^^ Did that for a while on quite a few test builds
Yes I know but I just want to see how Microsoft is going with these upgrades, I've done a couple of clean installs, I just want to see how far I can go without another clean install. This is not my main computer so it doesn't matter unless it just become a mess, at the moment it's limping but not defeated.
This is really the first time I've had a problem in quite some time, going back to 1030 or whatever it was that wrecked my SSD.
"I know but I just want to see how Microsoft is going with these upgrades"
FWIW They havent fixed the mail client and Groove Music instabilitys yet and occsional random freezing in general on all the builds that's been there since day one and when Groove showed up for that app , maybe Edge works better in 10547 or RTM ( now) I dont know I gave up on Edge a good while ago ! If it was a car crashing like that it would be criminal
I spent TOOO much time (months ) testing ,comparing and legitimatly verifying (documenting ) Win 10 things that didnt work or work right and pointing stuff out to them (along with a couple of fixes ) in the Insider discussion groups and feedback app ( when it worked now and then ) along with many others!
All we got was fanboy script and nonsense and the party line and fan boy haters chiming in , in return ! Only thing that gets any action outta them is declining sales and declining profits i.e. Windows 8 FAIL !
FWIW The MS storm troopers supressed legitimate critisism consistantly !
Since when did those omnipotent M.S. dictators ever listen to anybody anyway they are just a bunch of fanboys and MS storm troppers on Win 10 Iniders site *if they are MVP's or Microsoft people.or just the stupid fanboys *
Whole lot of us got them figured now ouside of the newbies . I aint the only one that feels that way either ! ☻
That being said the product is getting better but it ain't perfect neither is any other OS !
I'm just using the test builds and the RTM upgrades because I can right now they can otherwise go screw themselves ☻OTOH (at least at the consumer level ) the whole industry is like that .☻☻
Last edited by blutos cousin; 24 Sep 2015 at 00:55.
-
-
Yes I know but I just want to see how Microsoft is going with these upgrades, I've done a couple of clean installs, I just want to see how far I can go without another clean install. This is not my main computer so it doesn't matter unless it just become a mess, at the moment it's limping but not defeated.
This is really the first time I've had a problem in quite some time, going back to 1030 or whatever it was that wrecked my SSD.
The only serious thing I've encountered is that it's taking longer for bootup. I've kind of gotten used to the less than seconds to boot and now it's more like 30 seconds. 
Quote