diff --git a/chromeos/dbus/constants/dbus_paths.cc b/chromeos/dbus/constants/dbus_paths.cc
index 6737bb68f40233..db771906754868 100644
--- a/chromeos/dbus/constants/dbus_paths.cc
+++ b/chromeos/dbus/constants/dbus_paths.cc
@@ -18,7 +18,7 @@ constexpr base::FilePath::CharType kDefaultUserPolicyKeysDir[] =
     FILE_PATH_LITERAL("/run/user_policy");
 
 constexpr base::FilePath::CharType kOwnerKeyFileName[] =
-    FILE_PATH_LITERAL("/var/lib/whitelist/owner.key");
+    FILE_PATH_LITERAL("/var/lib/devicesettings/owner.key");
 
 constexpr base::FilePath::CharType kInstallAttributesFileName[] =
     FILE_PATH_LITERAL("/run/lockbox/install_attributes.pb");
diff --git a/docs/enterprise/enrollment.md b/docs/enterprise/enrollment.md
index d3f379a90d2f37..d8753424e06e37 100644
--- a/docs/enterprise/enrollment.md
+++ b/docs/enterprise/enrollment.md
@@ -19,7 +19,7 @@ on the login screen), if it is not disabled via device policy.
 Developers can reset ownership by running following commands as root in shell:
 ```
 pkill -9 chrome
-rm -rf /home/chronos/Local\ State /var/lib/whitelist /home/.shadow
+rm -rf /home/chronos/Local\ State /var/lib/whitelist /var/lib/devicesettings /home/.shadow
 rm /home/chronos/.oobe_completed
 crossystem clear_tpm_owner_request=1
 reboot