set service to manual broken?

[bindoet]

⚙️ Issue Checklist

• I have read the guidelines.
• I checked for duplicate issues.
• I searched for existing discussions.
• I checked for an existing pull request that addresses this issue.

📜 What part of Winutil are you having issues with?

Tweaks

📝 Provide a clear and concise description of the issue.

Is the manual service setting broken? Or is it part of the feature?

Previously, after debloating the service to manual, the service that was previously 140-160 could drop to the 60s (in Windows 10) and 80s (in Windows 11). However, now the service only drops to 98-99, and can even rise again to 100++.

🔄 Steps to reproduce the issue.

1. open winutil
2. tweaks
3. set service to manual
4. and run tweaks

❌ Paste the full error output (if available).

No response

🖼️ Additional context.

No response

[GabiNun]

why great another issue if there is already one anyway this isn't true

I have Tested this and here are the results

Stock Windows 11 25H2 (OS Build 26200.7462) Processes

Winutil (The Gabi Release) Windows 11 25H2 (OS Build 26200.7462) Processes

Winutil (Release 25.10.06 Before I have made a commit to winutil) Windows 11 25H2 (OS Build 26200.7462) Processes

you probaly recall those 80 processes before microsoft added a bunch of more things to windows

[Geckoonair]

I am not even on 25H2! I don't have this new stuff. All stuff this tweak did on my 23H2 build was 0 - zero. I took the version before and it applied. I just keep using the old version all good.

[GabiNun]

@Geckoonair

Stock Windows 23H2 (OS Build 22631.2428) Processes

Winutil (The Gabi Release) 23H2 (OS Build 22631.2428) Processes

Winutil (Release 25.10.06 Before I have made a commit to winutil) Windows 11 23H2 (OS Build 22631.2428) Processes

[Geckoonair]

Proofs what he said: „ Previously, after debloating the service to manual, the service that was previously 140-160 could drop to the 60s (in Windows 10) and 80s (in Windows 11). However, now the service only drops to 98-99, and can even rise again to 100++."

You are well above 100 all the times

[GabiNun]

@Geckoonair i used an older verison of winutil to a version before i have made a coomit so this is proof to show that my commits didn't break the tweak

[bindoet]

@GabiNun Here, I am still using the old version of WinUtil, and after I used the latest version of WinUtil, the results were like your screenshot (100++ services) in idle condition(1st boot, not opening anything).

[bindoet]

I just tried it with winutil 25.11.17 it's work fine. the latest one? no

[GabiNun]

@bindoet okay what dose the latest one processes?

[den1zalp]

I second the OP.

25.11.17 still works as now. Newer versions does not reduce the processes.

I formattes my computer yesterday and applied the script. Normally it would drop down to 90-92 processes.

However with the new version had made no effect on the processes. It was working with 110+ processes.

After applying the 25.11.17, it dropped down to 92 again.

Something is definitely messed up with the new version.

[mateus3c]

I tried 25.11.17 but it only reduced 10/20 services for me. I still have 300 services

[den1zalp]

I tried 25.11.17 but it only reduced 10/20 services for me. I still have 300 services

300 services are not normal by any means. Is your computer fresh formatted?

[Geckoonair]

You guys use service tweak + telemtry tweak? I feel like the disable telemetry above also disables services. If that is the case maybe that is broken. Didn't test it

[den1zalp]

You guys use service tweak + telemtry tweak? I feel like the disable telemetry above also disables services. If that is the case maybe that is broken. Didn't test it

What i am saying is, other people who made commitments to the version 25.11.17, were able to drop the processes without breaking any functionality of Windows.

On the other hand this version does not serve this utility's purpose anymore. It does not drop any processes.

This version should be taken down or at least get updated again. God knows what did that guy do with that new version.