Start with the pattern, not a guess
For a work computer, document the user, affected accounts, business impact, backup status, and who can authorize changes. A quick fix should not create an undocumented account, licensing, or security problem later.
Practical checks and decisions
Work from observation to one controlled change at a time. Stop when the next step could risk data, accounts, electrical safety, or additional hardware damage.
Track age, warranty, failures, and operating-system support
Document the affected user, endpoint, business process, downtime, account owner, and person authorized to approve a change. That prevents a quick fix from becoming an unmanaged business risk.
Prioritize computers tied to revenue or customer service
Identify dependencies such as Microsoft 365, shared files, line-of-business software, printers, backups, licenses, and outside vendors before credentials or devices are changed.
Budget for setup, data, applications, printers, and staff transition
Confirm backup status and the impact of a restart, migration, or replacement. Even a technically simple change may need a maintenance window, employee notice, or vendor coordination.
Replace on a plan instead of waiting for several emergencies at once
After the work, update asset, administrator, license, recovery, vendor, and support records. The result should be maintainable by the organization rather than known only to one person.
When a professional diagnosis makes sense
Escalate when downtime affects staff or customers, account ownership is unclear, backups or security controls are uncertain, or a change touches several users, vendors, or systems. Record business impact and the person authorized to approve work.
For hands-on or remote help, explore the service options related to this issue, or browse the Help Center for another guide.
