Solved Which commands do you recommend running right after clean installation

Do you recommend running "Rundll32.exe advapi32.dll,ProcessIdleTasks" command after windows installation?
What is the full command?
Which commands do you recommend running right after clean installation of Windows or periodically?

Just use a reputable memory cleaner rather than some random command.

I turn off PC with my tweaks, I run Setup 1/2 after a clean install and Cleanup. I also disable a performance killer = Defender.


11 uses 150 processes by default, I cut it by half.

TairikuOkami said:

Just use a reputable memory cleaner rather than some random command.

I turn off PC with my tweaks, I run Setup 1/2 after a clean install and Cleanup. I also disable a performance killer = Defender.

GitHub - TairikuOokami/Windows: Windows

Windows. Contribute to TairikuOokami/Windows development by creating an account on GitHub.

github.com

11 uses 150 processes by default, I cut it by half.

View attachment 132431

Click to expand...

I don't have memory usage problems because Windows handles it as best as it can. just want to have a stable installation.
As I understood, this command will run all scheduled tasks so I want to make sure this command will help me having a stable and fast OS.
I read your GitHub post and checked your bat files, but some of them are very strange for me, and I will never run such bat file before knowing every part of it. that's why I'm asking about the commands in different threads.
I will ask you about your bat file to make sure I can customize it for myself.
Thanks.

rundll32.exe advapi32.dll,ProcessIdleTasks runs any pending maintenance tasks. That's it. It doesn't run all scheduled tasks, and it's not some fancy memory cleaner as the Internet has suggested since, I dunno, the XP days probably.

pseymour said:

rundll32.exe advapi32.dll,ProcessIdleTasks runs any pending maintenance tasks. That's it. It doesn't run all scheduled tasks, and it's not some fancy memory cleaner as the Internet has suggested since, I dunno, the XP days probably.

Click to expand...

thanks for correcting me. I was searching in NTLite forum which I saw a member recommended this command to make sure everything is finished after installation and after that, Windows is ready to use.
that's why I asked for help.
do you recommend this command? does it cause problems?

I wasn't correcting you, per se, but I have seen for years people recommend this command as some kind of magical performance gain. I think maybe because it was mentioned in some performance testing docs, like this one for Windows 7: https://download.microsoft.com/download/7/e/7/7e7662cf-cbea-470b-a97e-ce7ce0d98dc2/win7perf.docx

It doesn't cause problems, but I'm not sure how much of a performance gain you get. Its intended purpose is to run the idle maintenance tasks, so that they don't run when you're doing other performance tests.

Sheikh said:

thanks for correcting me. I was searching in NTLite forum which I saw a member recommended this command to make sure everything is finished after installation and after that, Windows is ready to use.
that's why I asked for help.
do you recommend this command? does it cause problems?

Click to expand...

You didn't read the thread correctly. It's from a long running discussion about preventing DPC latency in audio playback.

hellbovine suggests in order to take a clean LatencyMon measurement, you need Windows as quiet as possible, and NOT running any background maintenance tasks to impact the results.

Therefore you run ProcessIdleTasks first. It's never been suggested to run as a post-install step.

garlin said:

You didn't read the thread correctly. It's from a long running discussion about preventing DPC latency in audio playback.

hellbovine suggests in order to take a clean LatencyMon measurement, you need Windows as quiet as possible, and NOT running any background maintenance tasks to impact the results.

Therefore you run ProcessIdleTasks first. It's never been suggested to run as a post-install step.

Click to expand...

Sorry I can't understand you. can you explain a bit simple for me? I'm not a pro... so I should not run that command after windows installation?

that topic is:

Guide: Installing Windows​

This guide walks users through the process of how to install Windows, as well as drivers, firmware, and other important aspects. It was created using Windows 10, but applies to others too. There are going to be a few places where the reader will need to do a little bit of their own research due to the nature of computers being so varied, but it is simple enough that by searching the internet or posting questions on this forum, someone with limited knowledge can still work through it, improving their skills and learning many great things along the way.

STEP 1: TAKING NOTES
STEP 2: INSTALLING FIRMWARE
STEP 3: DOWNLOADING DRIVERS
STEP 4: WINDOWS SETUP
STEP 5: INSTALLING DRIVERS
-> 5B) Reboot again, and the last step is to flush out all activity that is waiting silently in the background. To do this, click on "Start" then scroll down to "Windows System" and click on the folder. Right-click on "Command Prompt" then go to "More" and select the "Run as administrator" option. In the prompt enter "rundll32.exe advapi32.dll,ProcessIdleTasks & pause" without the quotes. This will take 15-30 minutes to finish, depending on the computer hardware, but after it is complete and the computer is rebooted, the overall amount of Windows resource usage will dramatically decrease, since there is less being used on background activities.

I won't speak for garlin, but what I'm saying is that you absolutely can run the command after Windows setup, but it won't have any benefit for long-term performance. It will run maintenance tasks (tasks that usually run when the system is idle), so that they don't run in the near term. But they will eventually run again; they are maintenance tasks afterall.

OK, I've re-read that section. You can't see the "Guide: DPC Latency" which proceeded this Guide (because hellbovine asked me to delete it).

Hellbovine copied that block of instructions from his DPC Latency thread. We don't always agree (and sometimes I strongly disagree as a IT pro), but what's missing is this is supposed to make a newly installed system feel faster. Normally there are always pending overhead tasks. Either you run them now, or wait later as Windows is designed to do.

Realistically, I don't see the point of invoking ProcessIdleTasks to make your PC spike in CPU & Disk for 10-20 min. and then return. Your PC will temporarily have a smooth experience for a while.

@pseymour is correct, it has no long term benefits. It's like eating dinner, and having to clean up. You can wash the dishes right after eating, or wait until an hour later to wash them. The dishes need to be washed at some time. Whether that makes you happier doesn't matter, because tomorrow you'll have dinner again.

garlin said:

OK, I've re-read that section. You can't see the "Guide: DPC Latency" which proceeded this Guide (because hellbovine asked me to delete it).

Hellbovine copied that block of instructions from his DPC Latency thread. We don't always agree (and sometimes I strongly disagree as a IT pro), but what's missing is this is supposed to make a newly installed system feel faster. Normally there are always pending overhead tasks. Either you run them now, or wait later as Windows is designed to do.

Realistically, I don't see the point of invoking ProcessIdleTasks to make your PC spike in CPU & Disk for 10-20 min. and then return. Your PC will temporarily have a smooth experience for a while.

@pseymour is correct, it has no long term benefits. It's like eating dinner, and having to clean up. You can wash the dishes right after eating, or wait until an hour later to wash them. The dishes need to be washed at some time. Whether that makes you happier doesn't matter, because tomorrow you'll have dinner again.

Click to expand...

your example
Now I understand.
thanks for the explanation.


@pseymour thanks.