I didn’t realize I had deleted the layout.ini file (C:\WINDOWS\Prefetch), just noticed that my boot time had increased markedly. I clean out prefetch regularly.
I tried running defrag -: giving me error message and would not run. Upon investigation I discovered that I had deleted layout.ini.
My googling told me that layout.ini could be rebuilt using Start/Run %windir%\system32\Rundll32.exe advapi32.dll,ProcessIdleTasks
I tried this many times without success it wasn’t until I came across the fact that Task Scheduler had to
be enable for this to work and bingo one rebuilt layout.ini file
Much much faster boot times and defrag ran without any problems.
Thanks for letting us know, it could possibly help others with the same problem.
That really is strange that in order for the command to work Task Scheduler has to be enabled, I can’t see any reason why task scheduler would have anything to do with it. I have task scheduler disabled as well, got fed up with it continually trying to connect and synchronise my system clock.
I too haven’t got a layout.ini file but haven’t tripped up when trying to use windows defragment without it. It is however very rare that I use windows defrag, more for the analysis after using RejZors Power Defragmenter - RejZors - eXcessive-software.tk Site. I have seen occasion when the power defragmenter had done the job in about the same time it took windows defrag to analyse a drive.
I’m a little confused, David. Doesn’t scheduling a boot-time scan use Task Scheduler for setting up a one-time task? Or is that handled somewhere else and therefore, like you, I can safely ditch the Task Scheduler?