Autopatcher usage - Easily tracked?


Recommended Posts

Hi, I'm just curious how easy it is to hide the fact that Autopatcher had previously been used on a system.

So far, I'm only aware of a registry key (which I delete after using autopatcher): HKEY_LOCAL_MACHINE\SOFTWARE\AutoPatcher

and clearing the explorer history and run history. Anything else I should be aware of?

I'm deploying Autopatcher from a network share but do not wish other power users or network administrators to know that I've been using Autopatcher :p Call me paranoid if you like XD

Link to comment
https://www.neowin.net/forum/topic/584040-autopatcher-usage-easily-tracked/
Share on other sites

well, delete HKLM\SOFTWARE\AutoPatcher (as you already did), also delete HKCU\SOFTWARE\AutoPatcher for any user account you ran autopatcher.exe on (if exists)

you should also scan the registry for 'autopatcher', there could be references to autopatcher.exe having been run, and things you install via autopatcher may store the dir they were installer from (so disguise the dir)

you should also clean out your temp dir's to make sure nothing is left behind, and make sure that C:\#AutoPatche Temp#\ (or whatever it's name is) is deleted. also make sure that if you installed the wallpaper modules, you delete the autopatcher related ones.

i don't see why on earth it's necessary though...

Knowledge is power in some businesses. Not sharing that knowledge will get you farther as you're the only one who has the knowhow. Kinda how I became our Image Guru. Nobody else had an interest in APXP so I took it and ran with it. Made images better, faster and quicker than our previous R&D manager, who was still installing through OPK and Windows corporate download site over a crappy wireless internet connection.

Hi,

I'm deploying Autopatcher from a network share but do not wish other power users or network administrators to know that I've been using Autopatcher :p Call me paranoid if you like XD

If the PC's do not belong to you or you are not responsible for their maintainance then you should take care when updating or repairing them with any tool, not just AutoPatcher.

The Admin's or Management may take a dim view of this and you could end up in serious trouble, including getting fired.

Personally if the PC's are not patched correctly then send a memo to the person responsible and leave it up to them to sort it out!

If the PC's are compromised or fail because of this then it's no longer your issue to worry about. Keep documentation of this so you can provide proof should this be needed ;)

Regards

Simon

Well, I'm the site admin for PCs in the building I'm working at. Just don't want the network management people to find out through SMS that I've been running autopatcher. I usually run Autopatcher (just for critical updates) before installing SMS. lolz

Well, if any system does crash, I'd just reinstall/ground-up again without running autopatcher :p

Hi,

If the PC's do not belong to you or you are not responsible for their maintainance then you should take care when updating or repairing them with any tool, not just AutoPatcher.

The Admin's or Management may take a dim view of this and you could end up in serious trouble, including getting fired.

Personally if the PC's are not patched correctly then send a memo to the person responsible and leave it up to them to sort it out!

If the PC's are compromised or fail because of this then it's no longer your issue to worry about. Keep documentation of this so you can provide proof should this be needed ;)

Regards

Simon

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Close, but it is for any application starting, not just during boot time. In fact, it probably will not improve boot time at all because during a boot, the CPU is already boosting, so a pre-boost wouldn't change anything. I agree that it isn't exciting (especially considering every other OS already does it), but it is a good thing, even if they are just playing catch up.
    • Any so called performance increase will be in milliseconds, which nobody will actually notice in real world usage.
    • All it does is use the CPU more efficiently during boot to speed up boot times. That's it. Yawn....
    • It's not a one or the other kind of thing. Software should run efficiently, and the operating system should appropriately manage the CPU clocks. You could have the best most optimized software on earth, and it will still run faster if the CPU does a better job of boosting as needed. All this is doing is pre-boosting the CPU based on user actions, instead of waiting for the normal detection mechanism to kick in. If the OS knows it is about to need more CPU, why shouldn't it use that knowledge? It's the same idea of downshifting before passing someone, instead of just burying your foot into the peddle and waiting for the transmission to figure out what you want to do.
    • Audacity 3.7.8 by Razvan Serea Audacity is a free, open source digital audio editor and recording application. Edit your sounds using cut, copy, and paste features (with unlimited undo functionality), mix tracks, or apply effects to your recordings. The program also has a built-in amplitude-envelope editor, a customizable spectrogram mode, and a frequency-analysis window for audio-analysis applications. Built-in effects include bass boost, wah wah, and noise removal, and the program also supports VST plug-in effects. You can use Audacity to: Record live audio. Record computer playback on any Windows Vista or later machine. Convert tapes and records into digital recordings or CDs. Edit WAV, AIFF, FLAC, MP2, MP3 or Ogg Vorbis sound files. AC3, M4A/M4R (AAC), WMA and other formats supported using optional libraries. Cut, copy, splice or mix sounds together. Numerous effects including change the speed or pitch of a recording. Write your own plug-in effects with Nyquist. And more! See the complete list of features. Audacity 3.7.8 changelog: #10688 Fixed an exception thrown when pasting into a newly-created track (Thanks, David Bailes (@DavidBailes)!) #10870, #10884, #10775, #10629 Fixed tone generation, waveform-scale setting, SetClip Name parameter, and clip-boundary command names for scripting and macros (Thank you, David Bailes (@DavidBailes)!) #11106 Fixed the loading of presets for the Distortion effect (A million thanks, David Bailes (@DavidBailes)!) #10947 Fixed paste into an empty audio track not preserving the source sample rate (Thanks, Juan Gabriel Colonna (@juancolonna)!) #10776 Allowed AltGr modifier in label and clip name editing (Thanks, Davide Peressoni (@DPDmancul)!) #9938 Added options to choose where silence is truncated (start/middle/end) (Thanks, Noah Rosenfield (@nosenfield)!) #9935 Added Podcast 2.0 chapters JSON export for label tracks (Thanks, Noah Rosenfield (@nosenfield)!) #10103 Improve UI on HiDPI displays on Linux/wxGTK (Thanks, Ivan A. Melnikov (@iv-m)!) #10099 Fixed MixerBoard Mute and Solo button display (Thanks, Ivan A. Melnikov (@iv-m)!) #10681 Fixed multichannel FLAC import #10999 Fixed envelope being broken after joining clips Download: Audacity 64-bit | Standalone ~20.0 MB (Open Source) Download: Audacity 32-bit | Standalone Download: Audacity ARM64 | Standalone View: Audacity Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • One Month Later
      highriskpaym earned a badge
      One Month Later
    • Week One Done
      highriskpaym earned a badge
      Week One Done
    • One Year In
      highriskpaym earned a badge
      One Year In
    • Week One Done
      FBSPL earned a badge
      Week One Done
    • One Year In
      Jim Dugan earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      499
    2. 2
      PsYcHoKiLLa
      198
    3. 3
      +Edouard
      155
    4. 4
      Steven P.
      84
    5. 5
      ATLien_0
      71
  • Tell a friend

    Love Neowin? Tell a friend!