Systems Engineer and Configuration
Management Analyst.

Postgrad degree is in computer science/cybersecurity, but my undergraduate is in archaeology. Someday, maybe, I’ll merge the two fields professionally!

I love true science fiction, as well as all things aviation, outer space, and NASA-related.

Lastly, Calvin and Hobbes is the best comic strip of all time!

Glad to be here trying out kbin and the fediverse.

This is my alternate account for Artemis, main:
@SpacemanSpiff

  • 0 Posts
  • 3 Comments
Joined 1 year ago
cake
Cake day: September 6th, 2023

help-circle
  • Install Linux on a USB stick or live CD. Boot into that OS and do exactly what you did last time.

    1. Unless they have gone into the firmware to prevent booting from anything but the HDD, this will will work and they can’t detect it.

    2. Once you make the changes and boot back into Windows they won’t know either. While the OS is offline their spyware does nothing. Once you boot back into Windows, it can’t run and can’t “call home”.

    As someone else said, they will know eventually that something is broken on your computer, that is, no data from your machine and it becomes a stale object. But they may not automatically believe it was intentionally disabled. You’d be surprised how low compliance numbers need to be in order to be satisfactory, and no security or monitoring solution is flaw-free. They may just blame the software. Many low-level IT admins are prone to this assumption in order to avoid spending a lot of time diagnosing the problem.

    Source: am a computer systems engineer