NVSlimmer - NVIDIA driver slimming utility

This tool is not for remove anything after driver installation, is for removing things on the driver package.

 

If there are leftovers to remove, uninstall the driver first.

 

all uncheked option will be removed/uninstaling automaticly

 

That's what I was thinking, so had to uninstall everything with ddu before installing slimmed driver

Is that true?

 

You can uninstall normally.

 

Thanks for this!

 

Well, not really.
I'd think for that to happen you'd need to select clean installation when installing the modified driver.

 

But what is essential for GF Experience functionality?
Somehow the comments here do not give sufficient information, or users do not share experiences.

I am pretty sure nvidia made the login requirement necessary for the user to avoid using shadowplay without using telemetry. Therefore with these options, GFE will not work.


Also, In the case of Geforce driver:
If you want to use msi afterburner, checkmark WMI provider setting in Miscellaneous.

 

That type of feedback is appreciated.
Honestly, I haven't tried many combinations of modules myself.
I just use the basic stuff.
That's why I asked for users to comment on their experience.
I'll see to add this info in a future release.

 

@uKER
Hey you might wanna looks at this post here:
https://forums.guru3d.com/threads/n...oad-and-discussion.426574/page-3#post-5667707

NvTelemetryContainerRecovery.bat isn't being installed with the Slimmer but other stuff he mentioned is present in the system.
I'm not sure if you'll have to make Slimmer edit the config.

 

Not sure I follow, those files are in the NvTelemetry folder of the installer so if you use a tool like slimmer or manually delete the folder it won't install that.

 

The thing is I used slimmer to install 430.64 and still have NvContainerRecovery.bat in C:\Windows. What I'm saying is If it can be safely removed why not do it with slimmer?

 

Ok, I checked for log in programdata and it wasn't there, didn't check C:\windows, yet.

Edit: I see what you're saying, in windows root dir, not sure how it got there, could be something with core driver, though I don't see anything with a quick look.

I would not worry about NvcontainerRecovery.bat, there nothing in there with telemetry.

 

Maybe it's a false alarm but I thought I'll report it here just in case.

 

hmm I have question about the program seeing I got tired of manually deleting folders.

.06 Defualts to having "Core Display Driver, Install Core, Physx" checked yes? does that mean only that stuff will be repakaged into the installer? and seeing I just need HD Audio I would just need to check that?

I only wwant Drivers/Physx/HD Audio. Also assuming the install option will just install what I have check in the slimmer with out repacking?

 

NV HD Audio driver is a known latency hog. Better off using MS supplied driver.

 

I hope someone can help me, I tried using this with the newest driver, picked almost the bare minimum because I wanted to use Geforce Experience but I get an error upon launching it 0x0003. I suppose I need to pick some other components but I don't know which ones are necessary, I had instaled GFE like a year ago but now this happened.

 

Has this been updated to cater for the RTX portion of the driver pack?

 

I gave it a try (v0.6). Loaded the driver package, hit repack....and nothing. It closed/crashed. The following two errors were in event viewer.

Also, a suggestion/request. Don't use the user temp folder at all? Keep everything portable, within the apps folder on my HDD, away from my SSD?

Code:

Level   Date and Time   Source   Event ID   Task Category
Error   6/5/2019 5:22:29 PM   .NET Runtime   1026   None   "Application: NVSlimmer.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Exception

Server stack trace:
   at NVSlimmer.DriverManager.Repackage(String fileName)
   at NVSlimmer.Form1.RepackageAsync(String fileName)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
   at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(System.Runtime.Remoting.Messaging.Message, Boolean)
   at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(System.Object, System.Runtime.Remoting.Proxies.MessageData ByRef)
   at NVSlimmer.Form1+DlgRepackageAsync.EndInvoke(System.IAsyncResult)
   at NVSlimmer.Form1.RepackageCallback(System.IAsyncResult)
   at System.Runtime.Remoting.Messaging.AsyncResult.SyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Messaging.IMessageSink)
   at System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.ThreadPoolCallBack(System.Object)
   at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

Code:

Level   Date and Time   Source   Event ID   Task Category
Error   6/5/2019 5:22:29 PM   Application Error   1000   (100)   "Faulting application name: NVSlimmer.exe, version: 0.6.0.0, time stamp: 0x5cc788f0
Faulting module name: KERNELBASE.dll, version: 10.0.17763.475, time stamp: 0x9877ee8b
Exception code: 0xe0434352
Fault offset: 0x0011c762
Faulting process id: 0x1f8
Faulting application start time: 0x01d51be4769798f1
Faulting application path: D:\NVSlimmer 0.6\NVSlimmer.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 4c74d9de-ae05-4cb3-8a01-c9462a961eb7
Faulting package full name:
Faulting package-relative application ID: "

 

That's weird.
Give me a link to the driver package you were using and I'll check it out.