Windows 10: Announcing Windows 10 Insider Preview Build 16241 PC + 15230 Mobile Insider

Josey Wales said:

Like I said HG as the build numbers get higher so do the bugs in direct proportion.

- we're workin' on that..

waltc said:

Thanks for catching that second "5" entry, Count...too late to change it now...

3) *Disable Prefetch Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters (because I have an SSD)...

5) Turn off disk defrag for drive c:\ (because I have an SSD) ...

Well, there's a prefetch parameter here, too--not just the Superfetch component--wear and tear on SSDs is measured by write/rewrite activity--that is the only way to measure the lifespan of these drives, everything else being equal, since there is no mechanical component. When you turn off the Superfetch service, these registry keys are not affected by doing that: enable Prefetcher, & enable Superfetch. Prefetch is a separate operation from Superfetch, and since I'm there I go ahead and turn off Superfetch as well, as you just Modify the parameter from 3 to 0 for both. Takes all of three seconds for the entire operation. Simply turning off the Superfetch service does not change these registry entries/values.

You are certainly right in that there is divided opinion about how helpful it is in turning off Superfetch and Prefetch with an SSD--but my own experiments in my system--limited, certainly--show no performance advantage at all that I can perceive between Superfetch/prefetch on and off with my SSD (while huge performance differences are perceivable using mechanical HDs, of course). So, I turn them off--as that undoubtedly increases the longevity of the drive to some extent as it stops any data-write activity related to the Superfetch/Prefetch settings being active. If they don't affect the performance of these drives when booting and running Windows, they aren't necessary, imo, while they demonstrably increase drive wear. Just my personal view, of course ...

Defragging an SSD unnecessarily is unnecessary, eh?... It doesn't seek like a platter drive, so defragging it like a platter doesn't serve a purpose, contiguous blocks mean nothing to an SSD--defragging could even slow it down, theoretically, and also contribute to unnecessary writes when the OS defrags automatically as it sees fit--it's the unnecessary activity that I object to, and that much isn't theoretical. My Samsung software tells me that I have enacted approximately 15.4 TB's of writes to the drive--which theoretically will handle ~75 TB's of data writes before it begins to fail. That leaves me about 6 more years of drive use at my current useage rates--In practice, though, the drive *might* last for 150 TBs--or 12 more years!... That's why limiting data writes would seem an advisable course to take.

That's my reason for limiting these things with an SSD as a boot drive. Yes, some people don't think it matters, but I think the logic behind turning these unnecessary drive writing activities off when they only serve to unnecessarily increase the writes on an SSD drive is sound. I mean the OS is smart enough to handle TRIM correctly--but not these other activities--for some reason, despite the fact they exist for mechanical platter drives exclusively.

Your suggestion about the shortcut arrow is one I can definitely commiserate with! But I use no tiles (ugh!--No Metro fan here!), and I don't use the Windows store (I mean, for what?...), and I have no issues with file ownership yet--knock on wood! I'm sure we all have our own lists of personal peccadilloes...

Just one point. It's not actually defraging if SSD is recognized as such. Only TRIM command is enacted but most modern SSDs have that in their firmware and do it (together with garbage collection and and wear leveling) automatically without OS intervention. I do turn off (when I remember) autodefrag on all disks. I have never had any HDDs go over 1% of fragmentation and it mostly sits at 0%. Only time I had to defrag a HDD is when I get someone elses's HDD that was with another OS to fix it or salvage files from it. For that I use third party program (Speed disk) that does it faster and with other options.
It is also not true that only SSDs wear out with usage, HDDs do too. One of my SSDs (el cheapo Kingston V300, 120GB) have over 75 TB and another, newer one has 22+ TB thru them. Still 100% as new. In mean time I had 2 HDDs go bad and one that inexplicably slowed down and I'll have to relegate it to backups because health is 85% but with no bad or replaced sectors, just bloody slooow all of sudden.

Kari said:

Edge bugs might not be the major issues you mean, but tweeting a question for #AskDona podcast, I got this reply:

Tweet

— Twitter API (@user) View on Twiiter

Tweet

— Twitter API (@user) View on Twiiter

Thanx K :)

I'm not so sure I agree with that methodology.. but then I'm a developer and the guys in the boardroom makes the rules.. either way, as long as the Autumn Update is solid.. it's all good.

@meebers @Edwin

I fixed my start menu issue where it's not showing the apps menu...




All I hdd to do was to stretch the menu itself. But I had to pin the app icons myself.




So now, it seems ok. Not that I ever use the apps menu. I was just alarmed that something was broken and something else might not be working properly. But so far. that's the only issue I noticed with the way I use this build.