---
title: "How should I configure Clean Slate to allow the Pharos Auto Updater to run?"
slug: "how-should-i-configure-clean-slate-to-allow-the-pharos-auto-updater-to-run"
updated: 2024-04-01T16:55:03Z
published: 2024-04-01T16:55:03Z
canonical: "kb.pharos.com/how-should-i-configure-clean-slate-to-allow-the-pharos-auto-updater-to-run"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.pharos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How should I configure Clean Slate to allow the Pharos Auto Updater to run?

I want the auto-update utility I distributed with Pharos Popup Packages to run and update client workstations when I upgrade.

How should I configure Clean Slate to allow the Pharos Auto Updater to run?

---

Customers should make the following adjustments to Clean Slate on the workstations:

1. Settings > Writeable Registry Keys
  1. HKEY_LOCAL_MACHINE\SOFTWARE\PHAROS\INSTALLED MODULES
  2. HKEY_LOCAL_MACHINE\SOFTWARE\PHAROS\UPDATER
2. Settings > Exempt Applications
  1. C:\PROGRAM FILES\PHAROS\BIN\UNIUPDATER.EXE
  2. C:\WINDOWS\SYSTEM32\SPOOLSV.EXE

These settings allow the update to occur and remain after a reboot.

## Related

- [Microsoft SQL Server Recovery Model Options for Pharos Blueprint and Uniprint](/microsoft-sql-server-recovery-model-options-for-pharos-blueprint-and-uniprint.md)
- [LDAP -> Blueprint Syncronization](/ldap-blueprint-syncronization.md)
- [Package Installation using a Windows GPO](/package-installation-using-a-windows-gpo.md)
- [“Invalid username or password” when using Omega with a Billing Gateway](/invalid-username-or-password-when-using-omega-with-a-billing-gateway.md)