Those 2 files are tricky. They’re more specifically based on the # of files that have been accessed/opened since boot-time and the last time they were created/modified. Some other unexplainable factors are involved. For example, every time I recreate them using my script, the sizes vary, sometimes in great numbers.
Yep, it’s been a while since we had a proper crazy system thread.
I think it’s better to use Task Scheduler, clean the system, reboot and leave it idle for 15 minutes. This will make the files smaller I think. Else they’ll get bloated by history etc. if using your script (at least that’s what I’ve observed).
Have you learned nothing from my last post? (:TNG)
Using that line will add unnecessary stuff in the file. For example, unless I can remember the line (which I can’t :-[), I’ll have to copy and paste from a .txt document. The path of this document will then be included in Layout.ini, making it bloated. I’ve found out by studying the .ini file that it seems to be the smallest if you use the clean-reboot-15-minutes method.
After using the “C:\WINDOWS\system32\Rundll32.exe” advapi32.dll,ProcessIdleTasks command, I never looked back 88)
How I really slimmed down the NTOSBOOT-B00DFAAD.pf: boot-time defrag with Puran. After I ran my script, it inflated to around the size you see now. Remember? My record of that file size at its lowest was either 78 or 87 KB :-TU