![]() (And editing the registry either manually or with a tool always involves a certain amount of risk… hence the usual advice to create a backup beforehand.) Similarly, you could – if you wanted to – clean the registry manually or use something like Ccleaner’s Registry Cleanup tool… but, again, it’s not going to hurt if you don’t. pf files related to Apowersoft… but it’s not going to hurt if you don’t. You could – if you wanted to – navigate to the C:WindowsPrefetch folder and delete any. Again, you can ignore them if you like… ‘cos they’re related to an application that you’ve uninstalled. I don’t have any experience with Comodo Firewall but within its interface there must be a way to remove the ‘rules’ related to Apowersoft. If you’re not having any issues with sound then you can ignore this. I was referring to the WDM Audio driver mapper (or Windows Driver Model Audio driver mapper), a virtual audio device, not your actual audio device. No issues with sound how do I ‘see’ what driver is being used for sound?Īpowersoft_AudioDevice is still registered in CurrentControlSet (and ControlSet001) (Also, it’s tedious searching through the filesystem manually looking for remnants, especially if buried within hidden AppData/ProgramData folders.) The reason for this is that it will catch the CLSID entries in the registry as well as cached install files that don’t include Apowersoft in the name. If that’s not possible then rmonroe36’s suggestion of using Revo Uninstaller is a good one, even if you have to use Revo Uninstaller to monitor a re-installation of Apowersoft screencast recorder before using Revo Uninstaller to uninstall it again. I think a System Restore to a date prior to the installation of Apowersoft seems the best/safest bet (especially if you are having problems with sound). Taking all this into account, I don’t believe that removal of the 8 registry entries (one of which shows you have an Apowersoft service installed and – it looks like – set to Manual) is the best way forward. I can also see from the 5th entry in your attached file that the “WDM Audio driver mapper” is set to Apowersoft’s virtual audio device driver. You also need to scan for Bytescout and multiple CLSIDs as well where Apowersoft isn’t mentioned. I had monitored the installation with InCtrl5 and this showed that a RegScan for Apowersoft isn’t sufficient. Have you checked your own C:WindowsSystem32drivers folder to see if the Apowersoft_AudioDevice.sys file is still present? It also showed me that the Apowersoft virtual audio device driver (Apowersoft_AudioDevice.sys) wasn’t removed either from the registry (where you can’t see the filepath in the reg file ‘cos it’s in hex format) or from the C:WindowsSystem32drivers folder. A scan for Apowersoft using RegScanner showed 105 registry entries left (2 of which were for changes to the Windows Firewall)… remarkably different to just the 8 shown in the text file you attached. I created a new Win 7 圆4 VM (I don’t use or have access to Windows 8/8.1) and installed then uninstalled Apowersoft screencast recorder so I could better understand what you are seeing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |