Delete C:\Windows\Installer\Razer? Over 13GB! | Razer Insider
Question

Delete C:\Windows\Installer\Razer? Over 13GB!



Show first post

33 Replies

Really not understanding how it’s that difficult to include something similar to this PowerShell one-liner at the end of the install.  It only took about 45 seconds to write.  It’s quite apparent that this is not a priority and has been pushed into the depths of the backlog if a story has indeed ever been created for the development teams.  Please feel free to pass this fix along to the teams.  They may use it free of charge.

Get-ChildItem -Path "$($env:windir)\Installer\Razer\Installer" | Where-Object -FilterScript { $_.Name -notin @("App","RazerInstaller.exe") } | Remove-Item

Other users…..please note that it must be run from an administrative PowerShell session because it’s trying to manipulate files under the Windows directory.  You would normally get an elevation prompt if you attempted to remove the files manually.

This another example of extremely simple solution and Razer seem to complete ignore anything happening in this thread. Please, make this a priority as I had to AGAIN clean up 10 GB of your crappy leftover install files. This is not a MINOR ISSUE whatsoever > this is bad installer code in its finest and needed to be addressed when reported EIGHT MONTHS AGO. The fact that it still isn't shows that you are either completely incompetent or do not take this seriously.

Really not understanding how it’s that difficult to include something similar to this PowerShell one-liner at the end of the install.  It only took about 45 seconds to write.  It’s quite apparent that this is not a priority and has been pushed into the depths of the backlog if a story has indeed ever been created for the development teams.  Please feel free to pass this fix along to the teams.  They may use it free of charge.

Get-ChildItem -Path "$($env:windir)\Installer\Razer\Installer" | Where-Object -FilterScript { $_.Name -notin @("App","RazerInstaller.exe") } | Remove-Item

Other users…..please note that it must be run from an administrative PowerShell session because it’s trying to manipulate files under the Windows directory.  You would normally get an elevation prompt if you attempted to remove the files manually.

Thanks for the script, 6.79 GB saved.

@Michelle-RazerCortexPC please add this script as part of the “Razer Central” app or something lol

 

 

Really not understanding how it’s that difficult to include something similar to this PowerShell one-liner at the end of the install.  It only took about 45 seconds to write.  It’s quite apparent that this is not a priority and has been pushed into the depths of the backlog if a story has indeed ever been created for the development teams.  Please feel free to pass this fix along to the teams.  They may use it free of charge.

Get-ChildItem -Path "$($env:windir)\Installer\Razer\Installer" | Where-Object -FilterScript { $_.Name -notin @("App","RazerInstaller.exe") } | Remove-Item

Other users…..please note that it must be run from an administrative PowerShell session because it’s trying to manipulate files under the Windows directory.  You would normally get an elevation prompt if you attempted to remove the files manually.

Thanks for the script, 6.79 GB saved.

@Michelle-RazerCortexPC please add this script as part of the “Razer Central” app or something lol

 

 

Well noted. Will let our engineering team know.

 

Again apologize for the inconvenience.

 

Thank you!

 

Michelle

Really not understanding how it’s that difficult to include something similar to this PowerShell one-liner at the end of the install.  It only took about 45 seconds to write.  It’s quite apparent that this is not a priority and has been pushed into the depths of the backlog if a story has indeed ever been created for the development teams.  Please feel free to pass this fix along to the teams.  They may use it free of charge.

Get-ChildItem -Path "$($env:windir)\Installer\Razer\Installer" | Where-Object -FilterScript { $_.Name -notin @("App","RazerInstaller.exe") } | Remove-Item

Other users…..please note that it must be run from an administrative PowerShell session because it’s trying to manipulate files under the Windows directory.  You would normally get an elevation prompt if you attempted to remove the files manually.

Thanks for the script, 6.79 GB saved.

@Michelle-RazerCortexPC please add this script as part of the “Razer Central” app or something lol

 

 

Well noted. Will let our engineering team know.

 

Again apologize for the inconvenience.

 

Thank you!

 

Michelle

Hey there!

 

Well noted. We will send this to our engineering team. Thank you for being patient. 

 

Apologize for the inconvenience.

 

Michelle

Hey there!

 

Thank you for sharing your issue with us here. My name is Michelle from the Razer Cortex technical support team. I am deligted to be of your assistahnce.

 

We sincerely apologize for the inconvenience this issue has caused you. Please kepp the “App‘ folder and “RazerInstaller.exe”, delete all other files. Please check the screenshot below:

 

Please let us know whether it helps. Thank you for your patience. 

 

Michelle

i have the same issue. but i also had 2 razerinstall.exes. i will leave both installers untouched

 

Hey there!

 

Thank you for sharing your issue with us here. My name is Michelle from the Razer Cortex technical support team. I am deligted to be of your assistahnce.

 

We sincerely apologize for the inconvenience this issue has caused you. Please kepp the “App‘ folder and “RazerInstaller.exe”, delete all other files. Please check the screenshot below:

 

Please let us know whether it helps. Thank you for your patience. 

 

Michelle

i have the same issue. but i also had 2 razerinstall.exes. i will leave both installers untouched

 

We apologize for the confusion this issue caused. We had reported this to our engineering team months ago. It will be resolved in our next big version. 

 

Thank you for your understanding and patient. 

 

Michelle

For those struggling with this still. Here is a Windows Task you can schedule to run automatically that will delete everything in that folder that isn’t the App folder or RazerInstaller.exe. Instructions below on how to set up that script.

CAUTION: This script works to do exactly as advertised. If Razer ever changes this folder structure you will need to turn off the schedule or it can / will cause issues. 

 


 

  1. Create the Batch Script:

    Open a text editor like Notepad and paste the following code:

    @echo off
    set "targetDir=C:\Windows\Installer\Razer\Installer"

    if not exist "%targetDir%" (
    echo Target directory not found.
    exit /b 1
    )

    echo Deleting files in %targetDir%...
    for %%I in ("%targetDir%\*") do (
    if /i not "%%~nI"=="App" if /i not "%%~nxI"=="RazerInstaller.exe" (
    del "%%I" /q
    )
    )

    echo Cleanup complete.

    Save the file with a .bat extension, such as RazerCleanupScript.bat.

  2. Test the Batch Script:

    Before scheduling the task, test the batch script by double-clicking it to ensure it deletes the correct files.

  3. Schedule the Task:

    Now, let's schedule this batch script to run monthly using the Task Scheduler:

    • Open Task Scheduler (search for "Task Scheduler" in the Start menu).
    • In the right-hand Actions pane, click on "Create Basic Task..." to open the wizard.
    • Follow the wizard to set a name for the task (e.g., "Monthly Cleanup Task") and a description.
    • Choose "Monthly" as the trigger, set the desired monthly recurrence pattern, and proceed.
    • Select "Start a program" as the action, then browse and select your batch script (RazerCleanupScript.bat.).
    • Complete the wizard by reviewing your settings and clicking "Finish."
  4. Additional Considerations:

    • Permissions: Ensure that the account under which the task will run has sufficient permissions to delete files in the specified directory.
    • Logging: Consider adding logging to your batch script (>> logfile.txt) to capture any errors or status messages during execution.

still a problem after all this time :) this company just doesn’t seem to care anymore, or if they do, hire new engineers because this is easily fixable in less than 20 minutes.

Reply