K2's Content Management Server install causes reboot loop
KB000088
PRODUCTK2.net 2003
SEE ALSO K2's Content Management Server install causes reboot loop
TAGSInstallation
Microsoft CMS
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.
| There is a known problem with K2 CMS components where a reboot will cause the MSI installer to fire each boot cycle. |
| Symptom: A system reboot will cause the MSI installer to fire. This results in continuous reboots. Cause: When the K2.net CMS installer was created it included a component called “Automatic Updates”. When the system boots up the “Automatic Updates” component attempts to check for updates and fails resulting in the continuous system reboot. Fix: The following workaround was found to resolve the issue. You are required to delete certain registry entries (see instructions below) that were created when the AutoUpdate software was installed. This will prevent it form starting up when the PC reboots. | |
| 1) | Open up regedit. |
| 2) | Navigate to: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionRun |
| 3) | Delete the entries for: ISUSPM Startup ISUSScheduler |
| 4) | Subsequent reboots should not attempt K2.net CMS re-installs. |
| The next version of the K2.net CMS installs does not include the AutoUpdate components. If, however a user updates to SP2 they will still need to disable the autoupdate manually because the update to SP2 will not remove the autoupdate components and the registry entries. | |
