Glad I took the risk to clean install everything just for this build. The most stable one for me so far
The build is a solid build coming from a totally different branch, the only thing I have a problem with is sometimes when you are idle at the desktop there's a quick flash of a CMD prompt, haven't figured out where its coming from cause its like a blink.
Blue screen is back, clean install. TH2 was the most error free for me. And memory compression is still a goddamn unnecessary feature that's constantly hogging resources.
See post #1 Download the ESD file AND the tool. The tool will decrypt the ESD and then you use it to make an ISO. Really simple. Coming from the actual current retail release, yes, this build is much better. Ironic that I left the stable build for a preview, pre release, just to get a stable copy of Windows 10
Too bad this build,language pack not work,when copying, deleting, or moving files there will be no progress dialog shown. ! When is new UPDATE ???
I don't really know what the point was of giving us a build with nothing new to play with, and known bugs that should have kept it from public view.
Testing the kernel. According to Microsoft 11082 contains some serious improvements to the kernel, which is the most important thing to test anyway. Without a stable foundation, there isn't a stable OS.
11082 IS NOT in Public View. It is an Insider Build meant for ONLY Insiders and NOT the General Public. It will be many months before the General Public gets Redstone. Starting in Jan Insiders in the Fast Ring could get 2 or 3 Builds a Month with a lot of Bugs. So if you don't want Bugs and you want a stable OS, change to the Slow Ring NOW
I am an insider. The insider program is a Public Beta program as opposed to an in house program. no one gets turned down. That is my point. There is nothing about this build that warranted releasing it into the wild.
Again, yes there is. Perhaps this build is even more warranted for release then many of the previous builds. Kernel changes need to be tested broadly.
There is absolutely nothing wrong with this release unless you use custom themes. I have installed this release in Hyper-V, and it is really good. Since none of the additional features do a thing for me, I have chosen not to use it as my main drive.
Does anyone recall the memory leak of maybe 5 or 6 months ago (unsure of the builds involved now). Used memory would gradually climb over a couple days to the point where most was used--even after you closed every single user program/task running on the system. It was a strange one, since tools like Task Manager and Process Explorer couldn't reveal specifically what the cause was (not a GDI leak, not a handles leak, not one particular task, etc). And it's not a matter of the System process (compressed memory) being behind it, since while that's sometimes several hundred MB, it never comes close to account for it. Well, it's back for me in this build, after several months of not seeing it at all. The screenshots below are after about 2.5 days use without reboot, but after all running programs are closed. 10GB of 16GB was still used...somehow. Of course, a reboot brings it down to around 10% usage, but then the cycle repeats over time. Yes, it's normal for some permanent memory escalation after days of use, but it shouldn't be anything this extreme. Any ideas?