New
#30
changed avatar lol...
ok so you think its normal that mine disappears. im trying to think if it would be a registry setting or is it becasue i remove the watermark..maybe rebuilding the index but i know that wont work..i actually like that feature..every build it lasts about an hour and it disappears right after...
18343 Snafu #1: This one's a doozy--and apparently so far it's only me who's seen it so far here (just my luck)...I've never seen this before, which makes it a new one, entirely: The offline install portion was ~22 minutes, just a wee bit slower than the last build--but after the obligatory reboot, I decided to update my AMD x370 chipset drivers, and upon the reboot from that...build 18343.1 reinstalled itself from Windows Update a second time right over the initial 18343.1 install--taking another ~22 minutes! As I mentioned--never saw this before today.
*After each build install, I always do a few things to correct the installation overwriting a few critical settings. I had to repeat them after the second concurrent install of 18343.1:
1) 1) powercfg -h off in an Admin Command Prompt (I don't need hibernate for anything, nor fast start booting, and never use sleep--this turns it all off in case the install turns it back on. Windows10 build installs most of the time do not turn on Hibernation if it is off in the upgraded build, however, a few times for unknown reasons a build install will turn on Hibernation--so I check it each new build)
2) Check sys restore and turn on if needed (It's always needed as every build turns it off.)
3) *Disable Prefetch Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters and turn off the Sys Main service--which is superfetch renamed (because I have an SSD boot drive which does not seek, true of all SSDs. Other reason to do these two simple steps each build is SSD drive longevity--SSD lifespan is measured in bytes written. My EVO 960 250 GB comes in with a life estimate of ~75GBs--or more, IIRC. I have put 6.6GBs in writes on the drive so far in the eleven months I've owned it, so I should easily get 10-12 years out of this drive, minimum. Of course that is ridiculous since I will have another SSD installed many years before that... It's the conservative side of me that likes to prevent the writes that I do not require, I guess.
4) Turn off disk defrag for drive c:\ and all OS-installed/recovery GPT partitions (because it's my SSD--and requires no defrag--no seek, etc., again--no sense writing to it unnecessarily, etc. Found it strange that Samsung built in a utility into Magician that takes you right to the Windows defrag options! Guess it makes a kind of sense--faster the drives wear out, the more of them we'll have to buy...)
6) Reset CoolSoft Virtual MidiSynth config via systray icon and set the correct sound device in the "Options" tab (these are often set improperly by a Win10 Windows Update Upgrade from previous build to current. If you want Midi support, this is the very best way to get it in Windows 10, imo.)
http://coolsoft.altervista.org/en/virtualmidisynth
7) Set Nahimic 3 to desired settings changed by new build install (Nahimic 3 is now handled via the Windows Store these days, and updates automatically--needs little to no attention after a new build install as it updates itself. But I still check it.)
https://www.microsoft.com/en-us/p/nahimic/9n36ppmp8s23?activetab=pivotverviewtab
8) Reinstall AMD GPU device drivers ( which I have found always without fail are muddled by a new Win10 build install--older GPU driver files mixed with the newer ones--so I do this after each and every new build install. Windows does nowhere near the complete job of installing the most up-to-date GPU driver--which I always get from the AMD site.)
Chipset
9) Reinstall AMD x370 core-logic chipset drivers (as they include a power plan specifically tuned to Ryzen cpus and platforms in Win10.)
Chipset
10) Cleanup C:\ to get rid of Windows.old (after a few days, of course, to make sure the new build is free of major problems.)
--Usually, I can remember these steps but I always pop open my list because I know I'll forget one or more of these steps! Besides the bug report here--hope this list may be of some help--it's certain that running with inferior hardware drivers may easily affect the stability of any Win10 system, imo. Your drivers will vary from mine, of course, but the principle is the same. First time I've had to do this twice for single upgrade build install!
You shouldn't need to disable defrag, and you should still run it on a SSD. In fact if you have an SSD it should show up in the defrag screen as a "solid state drive" and won't actually defrag it but perform a "trim"
How to ensure TRIM is enabled on Windows 10 to keep an SSD at top performance | Windows Central
That article explains better than I can.
Also the prefetch stuff, Windows 10 is suppose to be smart and not really use the prefetching feature if it's an SSD.
https://www.howtogeek.com/256859/don...hat-its-doing/
Agree with Walt about the Sys Restore. It saved my bacon more than once and have it always on. Thought at one time they had it fixed, but if it was, it only worked once or twice.
I've had the header for several builds, kinda' like it. It's missing the phone after install and can't get the phone to link up to the PC right now. Will probably write it up.
Thanks I'll try that next but I don't understand what file that would touch