Bugs Killed
Problems I have seen killed on Windows and Mac, with the steps that killed them.
Each page says where it comes from: a repair I made, a repair by someone from XL.net, or published sources you can open. The steps are one quick check away.
Windows
Windows sign-in could not find the domain; account was disabled and passwords were resynced
The user could not sign in because Windows said it could not find the domain. The technician used a local admin account, connected the VPN, re-enabled the disabled account after confirming the change was intentional, and reset the AD password to match the new Microsoft account password so sign-in worked again.
Killed once by someone from XL.net, on 2025-09-29.
Windows
Laptop would not charge because debris blocked the power port
The laptop would not charge because the power connector was not seating properly in the charging port. The device was replaced through an advanced exchange and the replacement laptop was set up successfully.
Killed once by someone from XL.net, on 2025-09-26.
Windows
PDF email attachments would not open because the file association was wrong
Email PDF attachments would not open. The technician reset the .PDF association to open in Edge and also set .doc files to open in Word.
- Windows
Killed once by someone from XL.net, on 2025-09-26.
Windows
Old driver left behind after a Windows 11 update causes a post-reboot error
After a Windows 11 update, an older driver was still present and conflicted with the newer driver, which caused an error to appear after each reboot. The technician removed the old driver and rebooted to confirm the conflict was gone.
- Windows 11
Killed once by someone from XL.net, on 2025-09-26.
Windows
PDF export used a variable Source Sans 3 font instead of the static font
Word documents were exporting to PDF with font rendering that did not match the original document. The issue was resolved by removing the Source Sans 3 variable font and installing the static Source Sans 3 version.
- Windows
Killed once by someone from XL.net, on 2025-09-25.
Windows
Windows update retry prompt after a failed scan on an older PC
The computer showed a prompt to run a scan and was behaving differently because Windows updates had failed on an older machine. The fix was to click Continue, let the scan finish, and let Windows retry the update.
Killed once by someone from XL.net, on 2025-09-25.
Windows
Xerox DocuMate 632 scanner driver repair and test scan
The DocuMate 632 scanner would not work until the drivers were repaired/reinstalled so the TWAIN driver was available again. A test scan was then run successfully, and the OneTouch software was removed.
- Windows 11
Killed once by someone from XL.net, on 2025-09-24.
Windows
Shared mailbox message times were shown in the wrong time zone
Message timestamps in the shared mailbox were offset by several hours. The mailbox time zone was updated to Central Time, which corrected the received-time display.
Killed once by someone from XL.net, on 2025-09-22.
Windows
Computer would not power on; user moved to a replacement PC
The original computer would not power on at all and was treated as a hardware failure. The issue was resolved by switching the user to a replacement PC and confirming it was working.
Killed once by someone from XL.net, on 2025-09-22.
Windows
Microsoft Teams desktop login failed; browser login was used as a workaround
Microsoft Teams would not let the user sign in on the PC. The technician could not fix the underlying update problem, but confirmed a browser login workaround.
Killed once by someone from XL.net, on 2025-09-19.