Announcing Windows 10 Insider Preview Build 15025 for PC Insider

Winuser said:

I wonder why the difference. My ESD created ISO is the same as Ztruker, 3,345,962 KB.

ESD based (option #2 in ESDtoISO) or 32bit?

Right click on the taskbar doesn't do anything for me. Anyone else seeing this?

f14tomcat said:

From 15019 release notes. Not pertaining to UUP per se, but.... Depends, I guess.

• Quicken 2016 will fail to run with an error stating .NET 4.6.1 is not installed. For Insiders familiar with Registry Editor, there is an optional workaround. Take ownership of the following registry keys and edit the “version” value to be 4.6.XXXXX instead of 4.7.XXXXX:

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\NET Framework Setup\NDP\v4\Client
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\NET Framework Setup\NDP\v4\Full
Note: Please take caution when editing the registry. Changing the wrong value can have unexpected and undesirable results.

I put a post here about how to implement this:
Quicken 2017 and TurboTax 2016 win10 ver 15007 registry changes.

Whoa! I just re-read the whole thread (first 38 pages through which I'd read yesterday, plus the 10 pages added since then). This has been the wildest ride on the Insider Preview express for quite a long while. I'd say we'd have to reach back to pre-1507 days to see this level of mystery and mayhem. If they still want to hit the 1704 time window for the upcoming next major release, it's clear they have a LOT of work to do.

After reading all the back'n'forth on UUP and how long somebody should be willing to wait for it to grind through to completion, here's my 2¢ worth on this subject. I've got two test machines. I'm willing to give 1 of them 6-8 hours to get through download and install, for the other no more than 2. My thinking is that anything that takes longer than 6-8 hours to install is an outright failure and I shouldn't have to devote the time necessary to keep checking on completion longer than that. Period. For the other machine, it's simply because 2 hours can slip into my working day without too much disruption, but having to ping-pong checking on 2 machines for longer than that *IS* a disruption, and I won't have it.

And there it is! I totally get Kari's insistence that some people stick it out to the bitter end, because MS needs the telemetry data. I guess if I had more VMs stood up for this kind of thing I could let them run ad infinitum. But I haven't done that yet, though now I suppose I probably should...

Thanks for all your input, observations, and ideas. Always a pleasure to see the community work things out. If only MS were as collegial with Insiders as we are with each other here!

Best,
--Ed--

Fafhrd said:

I've been checking out Tweaking.com windows repair,which basically puts back in place what should be there, using the catalog files, component store and and DISM, but invariably it finds problems with the Windows NTFS file structure, even with systems that are running nominally OK - broken simlinks and junctions - reparse points - that few people really bother about, or understand.

It seems to think that 15019 x86 is a little bit broken with: <Snip>

It's always been the case that the best cure for most of Windows' ills is a shutdown, a cup of coffee (and a fag "quick drag" in days long ago) then a reboot.

There were 4 engineers in a car that was chugging along on the verge of breaking down. They were arguing from their own fields of expertise and speculating about the problem.
The chemical engineer considered that the fuel mix was probably wrong, the electrical engineer that the alternator, plugs and distributor needed attention, and the mechanical engineer that it was wear on the bearings due to dirty oil, but the computer engineer considered the cure was simple, because he came across the problem every day.
He said that all that was required was to close all the windows, turn everything off and wait for a few minutes, then start it up again, open the windows and everything would be fine.

The old'uns are the best!

So, at the moment, Tweaking.com shouldn't be visited by those of us who may be old hands at testing Windows (whichever version) until more is known, or those who are really almost novices but think they're gurus?

Yes, sometimes the simple things are the best; however, I don't understand what happened with File Explorer's runtime, but I guess all I need to know is that a shutdown seems to have worked in this instance.

BTW, as I took TC's advice about the shutdown and wait a minute, I figured that I'd just go watch some TV with my husband, then come back and reboot.

Every problem I have tends to teach me something, so thanks to all you real gurus here to back us all up; you're very much appreciated.

kado897 said:

Right click on the taskbar doesn't do anything for me. Anyone else seeing this?

Working fine for me, Keith. I've set up the Quick Launch Bar and added numerous apps to it; right click to lock/unlock all taskbars works fine . . .