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
DICOM Viewer access restored on the virtual machine
The user could no longer access DICOM Viewer. The technician installed DICOM Viewer on the virtual machine and set up Windows App on the laptop to connect to that virtual machine instead of the old Remote Desktop app.
Killed once by someone from XL.net, on 2026-02-05.
Windows
Personal Windows laptop lost internet access after mitigation
The laptop had no internet access because it was disconnected during mitigation tied to the recent compromise. Kaseya and S1 were removed from the machine, and internet access was confirmed restored afterward.
- Windows
Killed once by someone from XL.net, on 2026-02-04.
Windows
Black screen and occasional freeze on a laptop during video calls
The laptop would intermittently go to a fully black screen and sometimes freeze, often during video conferences. The technician updated the video driver and installed other pending driver updates, then had the machine reboot after updates finished; this was reported as the fix.
Killed once by someone from XL.net, on 2026-02-03.
Windows
Failed to connect to a network printer
A network printer connection showed a 'failed' message. The printer was added to the machine and confirmed working.
- Windows
Killed once by someone from XL.net, on 2026-02-03.
Windows
Fake support alert shown in Firefox
A malicious website opened in Firefox and displayed a fake support alert telling the user to call a number. The site was closed and checked; it had not downloaded anything or changed Firefox settings.
Killed once by someone from XL.net, on 2026-02-02.
Windows
VPN access blocked by firewall geofencing policy
VPN sign-in failed with a "server is down" message because the firewall geofencing policy blocked the user's location. An exclusion was added, the VPN was retested successfully, and the change was later reverted when it was no longer needed.
Killed once by someone from XL.net, on 2026-02-02.
Windows
Loud fan noise with normal resource use and thermals
The computer was making an unusual loud fan noise. Technician checked resource usage and CPU, RAM, and SSD thermals, found no issue, and cleared about 50 GB from the C: drive to reduce possible processing stress.
- Windows
Killed once by someone from XL.net, on 2026-01-30.
Windows
Windows Defender-style lock screen with call-back number
Windows Defender was showing a lockout-style message telling the user the computer was locked down and to call a number. The technician removed malware instances from the PC and marked the issue resolved.
Killed once by someone from XL.net, on 2026-01-30.
Windows
HP OfficeJet Pro 8020 printer would not print until the port was corrected and the printer was reinstalled
The HP OfficeJet Pro 8020 was already installed but would not print. Changing the printer from a WSD port to the printer IP made a test page print, and after removing the duplicate/error entries the printer was uninstalled and reinstalled and then worked.
Killed once by someone from XL.net, on 2026-01-28.
Windows
IP address conflict kept the host unreachable over RDP/VPN
The host could not be reached over RDP while on the VPN because it was using an IP address that was also being seen as a printer. The IP was changed to the reserved address and remote access came back.
Killed once by someone from XL.net, on 2026-01-28.
Windows
Office apps would not sign into the shared conference-room computer
The shared Windows computer had an Office sign-in problem. The technician signed into Office successfully with the needed account, then signed it out again so the machine was left ready for the next user; they also noted that choosing "No, this app only" helps avoid the sign-in error when switching accounts on a shared device.
- Windows
Killed once by someone from XL.net, on 2026-01-27.
Windows
CargoWise install failed
CargoWise was not installed correctly. The technician installed CargoWise and confirmed it was working without errors.
Killed once by someone from XL.net, on 2026-01-27.
Windows
Downloaded documents would not open in the cloud desktop session
The user reported that downloaded documents were visible in the Downloads folder but would no longer open, and the automatic open-after-download behavior had stopped. The virtual desktop was rebooted, and the user was asked to test again; the ticket was then closed after confirmation.
- Windows
Killed once by someone from XL.net, on 2026-01-27.
Windows
Printer would not print until the driver was reinstalled
Printing to the printer was failing because the old access method was inaccessible. The technician installed the printer driver and set the printer as the default printer, and printing worked afterward.
- Windows
Killed once by someone from XL.net, on 2026-01-26.
Windows
Windows computer slow with Excel lag
The computer was reported as extremely slow, with Excel showing major delays. The technician ran system repair and cleanup actions, updated Windows and firmware, repaired Office, disabled background apps, cleared browser data, and removed unwanted applications, then asked the user to check performance and report back.
- Windows
Killed once by someone from XL.net, on 2026-01-26.
Windows
Argus Enterprise was missing after the weekend upgrade and had to be reinstalled
Argus Enterprise was no longer on the computer after the weekend upgrade. The technician got the updated Argus Enterprise 15.0 installer, installed the program, and confirmed it could be signed into and used.
Killed once by someone from XL.net, on 2026-01-26.
Windows
Notes app and data were restored
The Notes app had an issue and the technician restored the app and its data. No root cause or command line was recorded in the ticket.
- Windows
Killed once by someone from XL.net, on 2026-01-26.
Windows
Chrome crash on a remote desktop blocked site access
Chrome on the remote desktop crashed and became unresponsive, and the site reported that it was not secured. Restarting the virtual desktop cleared the problem and the site opened again.
Killed once by someone from XL.net, on 2026-01-26.
Windows
I: mapped drive was missing on a laptop
The I: drive was no longer visible or accessible on the laptop. It was mapped again from the available drive information and access was confirmed.
Killed once by someone from XL.net, on 2026-01-26.
Windows
ZIP files had the wrong or missing default app association
The default app association for ZIP files was removed or reset. The technician reset the file association and noted that a reboot was required before checking again.
- Windows
Killed once by someone from XL.net, on 2026-01-23.
Windows
Deleted folder restored to a shared path
A folder deleted from a shared path was recovered and placed in a folder named Restored at the requested location.
- Windows
Killed once by someone from XL.net, on 2026-01-23.
Windows
Print queue was stuck and the printer had to be reinstalled by IP
The printer would not print until the print queue was cleared and the printer was removed and reinstalled using its IP address. Printing was then tested and confirmed to work.
Killed once by someone from XL.net, on 2026-01-22.
Windows
VPN sign-in failed until the synced server password was corrected
VPN sign-in was failing. The server login password was corrected on the domain controller, after which VPN access worked; network drives and Office sign-in were also checked.
Killed once by someone from XL.net, on 2026-01-21.
Windows
Printer selected in Windows but jobs never reached the device
The printer could be selected, but print jobs were not reaching it. The printer was reinstalled using a TCP/IP port and a test print was confirmed to work.
Killed once by someone from XL.net, on 2026-01-21.
Windows
HP M110w printer repeatedly goes offline and shows the driver as missing
The printer kept going offline and Windows reported that the driver was not installed. It was reinstalled over USB with the official HP driver package, and test pages printed successfully before and after a reboot.
Killed once by someone from XL.net, on 2026-01-21.
Windows
PowerPoint slide text box font size kept reverting to 11 pt
Two text boxes on a slide did not match: the added text kept changing back to 11 pt instead of staying at 10.5 pt. The technician matched the formatting between the boxes and made minor adjustments so both stayed at 10.5 pt and the text fit properly.
Killed once by someone from XL.net, on 2026-01-21.
Windows
Network printer failed after IP change
A network printer stopped working. The printer IP was restored to its original address and the printer was reinstalled on the machine, and it worked.
Killed once by someone from XL.net, on 2026-01-20.
Windows
Remote Desktop disconnected repeatedly because of unstable network connectivity
Remote Desktop sessions were dropping and could not reconnect. Network testing showed periodic ping spikes and packet loss; restarting the modem stabilized the connection and removed the packet loss.
Killed once by someone from XL.net, on 2026-01-20.
Windows
Zoom meeting freeze followed by system slowdown
The computer froze near the end of a Zoom call and then became very slow. Logs showed a memory leak around the meeting start; scans repaired corrupted files, hardware drivers were updated, and the machine was rebooted and then ran stably.
- Windows
Killed once by someone from XL.net, on 2026-01-17.
Windows
Shared printer stopped working after the print server was decommissioned
Old shared printer instances no longer worked because they were installed from a print server that had been decommissioned. The old instances were removed and the printers were reinstalled as standard network printers, then both printed successfully.
- Windows
Killed once by someone from XL.net, on 2026-01-16.
Windows
Permission error when saving emails from a folder
Saving some emails failed with a permission error. The technician found the issue was missing access to the folder the emails were pulled from, added the user to that folder, and confirmed the permission errors stopped.
- Windows
Killed once by someone from XL.net, on 2026-01-15.
Windows
Phone system needed a firewall rule updated to include an additional IP
The phone system stopped working even though internet access was still up. The firewall rule was updated to include another IP address, and the customer was asked to test the phone system afterward; the ticket does not record the test result.
Killed once by someone from XL.net, on 2026-01-14.
Windows
Restart and shut down failed until the user profile was rebuilt
The laptop would not restart or shut down through the normal power options, and forced shutdown was also troublesome. The old domain user profile was backed up, removed, and recreated; user data was restored and the power features then worked correctly.
- Windows
Killed once by someone from XL.net, on 2026-01-14.
Windows
Camera blocked by a privacy cover in video calls
The camera would not turn on in Zoom and Teams, and the device reported that the camera was blocked or turned off by a switch or button. Windows updates and firmware updates were installed, and the built-in camera was found to have a lid cover/privacy shutter, after which the issue was resolved.
- Windows
Killed once by someone from XL.net, on 2026-01-14.
Windows
Network drives were unavailable and file opening was slow
Access to the network drives was restored on the laptop. That was the confirmed fix for the slow file-opening behavior tied to waiting on a connection.
Killed once by someone from XL.net, on 2026-01-14.
Windows
Xerox printer stopped printing because it was using a WSD port
A Xerox printer showed an error and then a blank queue on the workstation. The printer was reconnected over TCP/IP instead of WSD, and a test print confirmed it worked.
- Windows
Killed once by someone from XL.net, on 2026-01-13.
Windows
Chrome print destination was set to Save to PDF
Printing in Chrome opened a save/cancel screen instead of sending the job to a printer. The print destination was changed from Save to PDF to the printer, which restored printing.
- Windows
Killed once by someone from XL.net, on 2026-01-12.
Windows
AutoCAD 2020 reinstalled and activated
AutoCAD 2020 was reinstalled and activated. License activation was completed by signing in to the AutoCAD account, and the issue was confirmed resolved.
- Windows
Killed once by someone from XL.net, on 2026-01-12.
Windows
Slow internet only while connected to VPN
Internet speed slowed down at home only when connected to VPN, and returned to normal when VPN was disconnected. The technician disabled Receive Side Coalescing (RSC) on the Ethernet adapter, which resolved the issue.
Killed once by someone from XL.net, on 2026-01-12.
Windows
Virtual machine freezing and slowness after missing updates
The virtual machine was freezing and applications were slow even after rebooting. The technician installed the missing important updates and restarted the computer, which restored normal performance.
- Windows
Killed once by someone from XL.net, on 2026-01-12.
Windows
Printer showed Ready but did not print
A new printer was connected and showed Ready in Windows, but print jobs would not start or produce output. The printer was reinstalled and the problem was resolved.
Killed once by someone from XL.net, on 2026-01-09.
Windows
Touchpad and speakers stopped working on a laptop; BIOS/firmware and driver updates fixed it
The touchpad had stopped responding and the speakers had not worked on the laptop. The technician installed pending BIOS and firmware updates, reset the mouse driver, and updated the Realtek drivers to the latest version, which resolved both issues.
Killed once by someone from XL.net, on 2026-01-08.
Windows
Laptop would not power or connect through the docking station; the laptop was replaced and set up again
The laptop showed an insufficient power message when connected through the dock, and the dock light stayed yellow. The issue was treated as a likely hardware problem after testing with known working docking stations, and a new laptop was set up.
Killed once by someone from XL.net, on 2026-01-08.
Windows
Black screen on arrival; forced power-off and restart restored the display
The machine showed a black screen when it was brought into the office. Holding the power button for more than 10 seconds and then restarting restored the screen.
Killed once by someone from XL.net, on 2026-01-08.
Windows
Auto-lock did not trigger after inactivity
The affected account was not auto-locking after 5 minutes of inactivity. The auto-lock settings were updated and then verified by leaving the machine idle for 5 minutes until it locked.
- Windows
Killed once by someone from XL.net, on 2026-01-07.
Windows
VPN sign-in fails immediately with "login failed"
The VPN client returned "login failed" right after the password was entered. The connection was restored by confirming the credentials, moving the PC to a hotspot-only connection, starting the VPN, and approving the sign-in from the phone.
Killed once by someone from XL.net, on 2026-01-07.
Windows
Rhino 8 freezes when accessed
Rhino 8 was freezing when it was opened or accessed. The application update was completed, the laptop was restarted, and the freeze no longer reproduced.
Killed once by someone from XL.net, on 2026-01-07.
Windows
Teams sign-in failed until Microsoft Authenticator was reset on the new phone
A seasonal external user could not complete sign-in for Teams after moving to a new phone. Support reset Microsoft Authenticator and reconnected it on the new phone, and sign-in was confirmed to work normally.
Killed once by someone from XL.net, on 2026-01-06.
Windows
VPN login fails with 'login failed' after password entry
VPN sign-in was failing immediately after password entry with the prompt showing 'login failed'. The issue was traced to a certificate problem and was resolved by the escalations team.
- Windows
Killed once by someone from XL.net, on 2026-01-06.
Windows
Shared drive access restored after password reset and credential update
Access to the shared drive failed until the password was reset and the updated credentials were entered again on the server. After that, access was verified.
Killed 2 times by someone from XL.net, most recently on 2026-01-05.