People complain about 9901... but hey! 1) It's a pre release software 2) It's not a public build So... 1) Stay on public builds (picked by MS, judged stable enough for a daily usage) 2) Don't install leaked builds (or at least in a virtual machine)
r as getting the Apps to work hat get stuck at the splash screen, you have to open a metro app, minimize it, then click task view and close the middle view, this works some of the time...and for the clock app, has anyone been able to make this work?
Yea, the bugs in this one are really major...the worst kind, imo. Sporadic. Untraceable. Windows has always been like a set of dominoes...when one goes down it pulls a bunch more down, but the resulting error message may well identify the middle domino instead of the initial domino to fall in the chain.... So what we're fixing is not actually the root of the problem, etc. Been there, done that. I'm like you, I suppose, in that I never say never... But I am going back to 8.1 for awhile...Throwing salt into the 9901 wounds is the fact that Microsoft is spreading it around that if you install 9901 then you won't be privy to any more updates or the next new build--but Gee, if they do the sensible thing and release the next build as an .iso (like they've they've had the good sense to do) why couldn't someone update from 9901? Seems like a bizarre thing to say about 9901, doesn't it? I mean, Microsoft had to have released the thing to *somebody* else it would never have been leaked, right? So is Microsoft saying that the poor slobs who legitimately were blessed with a legal 9901 are SOL themselves when it comes to the next build? This has been a really puzzling build--had no trouble with the others...
Problem is that in this case I pity the poor folks who got this "private" build 9901... This is one Microsoft should have kept in-house, imo.
You are so right. I have got it to run smooth again, but I am also waiting on the next crash that I know is coming. I know it does have something to do with Nvidia driver, been playing and modding the 64 bit Vista driver. I don't get it the 32 bit driver works perfect with both 32 bit builds. I don't see much difference between the 32 bit and 64 bit driver so it has to be within Windows that is causing the problem.
I think we've had so many "pretty good" beta builds in the last few years that people forget about the beta part. IMO 9888 and 9801 are very erratic builds that present many challenges to those who install them. I liken it to sneaking into a car factory, jumping in a car 1/2 way down the production line and wondering why the radio doesn't work, the wipers don't shut off, and some ugly chick is in the back seat. In a couple of weeks we'll have a new more-ready-for-prime-time build to play with. One thing about us beta testers, we all have the patience to wait...
Been using build 9901 for the last week and i love it very stable for me and everything works as intended only one problem is that my sound driver crashes causing a Diagnosis which turns it back on.
Same problem here. To get around this bug I followed these instructions on winaero.com and it installed fine. : To install .NET Framework 3.5 in Windows 10, do the following: Insert your Windows 10 DVD, or double click its ISO image, or insert your bootable flash drive with Windows 10, depending on what you have. Open 'This PC' in File Explorer and note the drive letter of the installation media you have inserted. In my case it is disk D: Now open an elevated command prompt and type the following command: Dism /online /enable-feature /featurename:NetFX3 /All /Source:\sources\sxs /LimitAccess Replace d: with your drive letter for Windows 10 installation media. You are done! This will install .NET framework 3.5 in Windows 10.
Installed Windows 10 TP Build 9901 again after the VB Crash and now try to install Andy Android first. I installed also VB latest version up front, Andy is just now 'repairing' that VB again and I think the outcome will be bad and not work again! Hopefully I'm wrong! If not, I'll go back to 9879!
Thanks! Will go back to 9879 now because to many major problems with this build 9901 (for me!!). Many of my apps getting problems while impossible to run, or problems while running! All of those were working well on 9879! So, only solution (for me) is to go back and wait for the next build release (from MS only) and see that problems are solved or not!!
I don't look at it as complaining, just sharing your experience. I think we all know what we're playing with here.
The only issue I have with 9901 is that the pc keeps coming up with a message every so often saying that the computer will restart in 1 minute. and no way aroundit that i can see
Unable to install office 2013. My wifi connections also get some error and it wil not show any connections when i tried to install office. Only restating the pc rectifies the problem
I got O2013 installed, but it wouldn't activate with the 3 day trial key, had to use one of my Tech Net keys. Build 9901 is interesting, if nothing else. I think MS made it a "sneak leak" just to mess with our heads. Think about it - 9+9+0+1 = 19............9+1 = 10. AND if you add the numbers in reverse, you get the same answer. Thank you Sgt. Pepper.