Announcing Windows 10 Insider Preview Build 14393 for PC and Mobile Insider

magilla said:

I had similar event, at time of completion of download and as restart was beginning but it flashed on screen, then was gone, and reboot started without a flaw and installation was without incident. Maybe a bug in install routine. I reported it but did not get screen shot. This is first time I have had this happen.

That's a relief, at least I am not the only one. Submitted feedback with pic

magilla said:

Did you report to insider hub? Since you have screenshot might be helpful.

Yes...see above

First the good stuff:

Smooth WU upgrade install to 14393 from 14390--'bout ~24 minutes to *upgrade* and I have a robust system I upgrade with each new OS build, with well over 200 games and program applications installed and brought forward with each new build--not to mention dozens of device drivers and various utilities, as well! This is one thing that has struck me rather forcefully throughout the Insider's program recently--don't know how many folks share my memories of even Win7 starting to slo-o-o-o-o-o-ow down in boot times, program opening/loading times, and especially *OS upgrade* times, the more software (applications, utility programs & games) installed into a given system!

It was rather amazing, I thought, how slow-w-w-w-www even Win7x64 would get the more programs and other software were installed into the system--whereas a "clean install" of Win7 with nothing installed aside from the OS ran like greased lightning compared to boot and application load times for Win7x64 with dozens or hundreds of programs installed (large and small.) Basically, the rule of thumb for so many years with Windows (that I cannot count them all) was that the more programs installed into a given Windows installation (and I certainly don't mean only the ones that load in the startup sequence and/or show in the systray...!...;)) the slower the system would do a variety of everyday things, like loading and running programs and the rest of it. As much as this was discussed in various Windows forums for years I have no doubt everyone in these forums is intimately familiar with the concept....;) As always the advice was to every so often do a clean install and just reinstall everything from ground zero...a time-consuming endeavor that had to be repeated every so often, no choice about it for a regular user and software customer wanting to keep his system running optimally.

What has me fascinated a bit about all of this is that I deliberately have been *upgrading* one build on top of an earlier build--and all the while, build after build, I've been adding applications and other software on a fairly regular basis so that now I've got terabytes of installed program data spanning a variety of drives

At any rate it's only recently hit me how much faster--how much "incredibly faster and more efficient" (I'm tempted to say)--Win10x64 is over previous versions of Windows to date in this regard! There is virtually no difference in boot times between a clean-install Win10x64 build and the same build heavily installed as mine is with tons of 3rd-party software installed! This is an upgrade install process going for most of the last year in my system--I think I started over with with a clean Win10x64 install 10-12 months back, and I've been adding to that regularly--and consistently upgrading when the next build becomes available--and my boot times and my application load/run times haven't diminished even 5% I'd estimate since my last clean Win10x64 install!

That's a fairly huge improvement over former versions of Windows and indicates to me that Win10x64 (I haven't worked with x86 Win10) no doubt incorporates a superior memory management structure than the company has ever utilized in Windows versions prior to Win10x64--It seems as if Microsoft is simply using system ram, using more of it and far more efficiently, than in any Windows build before. Early versions of Windows memory systems were heavily page-file oriented, obviously, with ram being in short supply, in order to page out to hard drives when system ram was scarce. The more that happens the slower things get, obviously. And when a memory system is built around that principle of design...

OK, that's about it...feel free to dissent--that's what opinions are for...;) I know that some of it is caused by the fact that I'm using an SSD boot drive for Win10x64 and have been for more than year--but what I am speaking of here is mainly the percentages! Even accounting for the SSD's much better performance, Win10x64, at least in my system, is holding up its performance better than Win7x64 ever did, through upgrade after upgrade and the installation of hundreds of of applications, games and utilities--there is a lot of difference in that regard, imo.

__________________________________________________

Now for the not-so-hot-stuff in 14393...;)

Only "fly" in my particular ointment is the continuing SHA-256 AMD Crimson GPU driver certificate-signing problem that has afflicted all builds of Win10 & all AMD Crimson driver versions since the first AMD GPU driver signed with a SHA-256 certificate. It's not *that* bad an issue atm since Win10x64 will still install and run the SHA-256 signed certificate drivers so long as the user turns off secure boot...! Which of course defeats the entire purpose behind moving the OS to UEFI in the first place, imo--if secure boot must be turned off.

Anyhoo...not too many more builds before this year's 'hot tamale' OS release is ready for its official debut, eh? Shaping up and coming together nicely, imo.

(It's late and any errors are entirely my own!)