The fall Creators Update #1709 and PrimoCache

[BonzaiDuck]

After I struggled through troubleshooting the #1703 CU with Windows 10, I had enough caution and reticence about another CU to defer installing #1709 for up to a year. Somehow, Win Update seemed to take over in the matter of that decision, and I could only cross my fingers knowing that I had good Macrium backups of the entire system.

My system is a dual-boot Win7/Win10 configuration, and the #1703 CU had borked my dual-boot menu. I was able to fix it with a utility like Macrium Reflect or MiniTool.

Somehow, the #1709 upgrade went without a hitch, leaving the entire configuration operating perfectly. Did anyone have more troublesome experiences? I noticed that the caching tasks were no longer linked to the source drives, and I had to re-enable them. But that was the only annoyance in the upgrade.

[minhgi]

My daily laptop already on Windows Spring Creator Updates 17715 and don't have any issue. Other than reenabling the drive to be cached; I don't have any issue after the upgrade. Just normal cleaning of the old windows archive folder and upgrade download. It seem this version of Windows worked even better when using with Primocache.

[BonzaiDuck]

My daily laptop already on Windows Spring Creator Updates 17715 and don't have any issue. Other than reenabling the drive to be cached; I don't have any issue after the upgrade. Just normal cleaning of the old windows archive folder and upgrade download. It seem this version of Windows worked even better when using with Primocache.

As I said, that was my experience with it for the Fall update. Whatever problem I'd had was either due to (a) the Windows 1703 creators install process, (b) Romex 2.x, or (c) a combination of the two.

If the #1709 upgrade didn't do anything but delete the caching tasks, then there's the chance that the next one will work properly also.

I'd blown about $600 on my NVME "PRO" drive, another $130 for an EVO NVME used for caching, and an additional $180 to double my RAM on this system. I've had people say "you don't need more than 500MB/s . . . " and other remarks. I just reply that I wanted to see what I could build -- and I built it.

Helluva rock-solid system now. A WEI freeware plug-in for Windows 10 now shows this for the 4.7 Ghz SKYLAKE with 32GB RAM, a GTX 1070 and the drives I mentioned:



Usually, with the WEI, most systems I remember are limited to their storage scores. This is a "new ballgame," it seems.

It's reasonable to hear people say that the WEI in some respects doesn't prove a lot even for an OC'd system. No disputing that, but these scores are otherwise stellar.

[minhgi]

"Helluva rock-solid system now. A WEI freeware plug-in for Windows 10 now shows this for the 4.7 Ghz SKYLAKE with 32GB RAM, a GTX 1070 and the drives I mentioned:"

Yeah!! Your setup is what I have for my personal desktop.

1) Gigabyte Z210N Gaming 5/ i7-6700k / 32 GB 2666 MHZ / GTX 1070 / Raided 1 C and D / going to raid 0 my two Samsung 850 PRO tomorrow

Also have a working computer with similar spec but with Sam 960 Pro.

Will see if I can match your performance spec on my personal computer just for comparison.

[minhgi]

Not particularly happy with my disk benchmark on WD Velociraptor TB Raid 1. Never did any kind of benchmark since having it build in 2015.