r2modman 3.1.48

A guide to uninstall r2modman 3.1.48 from your PC

r2modman 3.1.48 is a Windows application. Read below about how to uninstall it from your PC. The Windows release was developed by ebkr. You can read more on ebkr or check for application updates here. The program is usually located in the C:\Users\UserName\AppData\Local\Programs\r2modman folder. Keep in mind that this location can differ being determined by the user's preference. C:\Users\UserName\AppData\Local\Programs\r2modman\Uninstall r2modman.exe is the full command line if you want to remove r2modman 3.1.48. r2modman 3.1.48's primary file takes around 120.61 MB (126472192 bytes) and is called r2modman.exe.

The following executable files are incorporated in r2modman 3.1.48. They occupy 121.15 MB (127033356 bytes) on disk.

• r2modman.exe (120.61 MB)
• Uninstall r2modman.exe (443.01 KB)
• elevate.exe (105.00 KB)

This page is about r2modman 3.1.48 version 3.1.48 alone. Many files, folders and Windows registry data can not be deleted when you remove r2modman 3.1.48 from your PC.

Directories that were left behind:

• C:\Users\%user%\AppData\Local\r2modman-updater
• C:\Users\%user%\AppData\Roaming\r2modman

The files below remain on your disk by r2modman 3.1.48's application uninstaller when you removed it:

• C:\Users\%user%\AppData\Local\Packages\Microsoft.Windows.Search_cw5n1h2txyewy\LocalState\AppIconCache\100\ebkr-r2modman
• C:\Users\%user%\AppData\Local\r2modman-updater\installer.exe
• C:\Users\%user%\AppData\Local\r2modman-updater\pending\r2modman-Setup-3.1.48.exe
• C:\Users\%user%\AppData\Local\r2modman-updater\pending\update-info.json
• C:\Users\%user%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\r2modman.lnk
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\data_0
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\data_1
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\data_2
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\data_3
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000005
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000006
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000007
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000008
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000009
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_00000a
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_00000c
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_00000d
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_00000e
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_00000f
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000011
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000012
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000013
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000014
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000015
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000016
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000017
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000018
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000019
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_00001a
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_00001b
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_00001c
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_00001d
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_00001e
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_00001f
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000020
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000021
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000022
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000023
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000024
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000025
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000026
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000027
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000028
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000029
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_00002a
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_00002b
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_00002c
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_00002d
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_00002e
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_00002f
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\f_000034
• C:\Users\%user%\AppData\Roaming\r2modman\Cache\index
• C:\Users\%user%\AppData\Roaming\r2modman\Code Cache\js\index
• C:\Users\%user%\AppData\Roaming\r2modman\Code Cache\wasm\index
• C:\Users\%user%\AppData\Roaming\r2modman\Cookies
• C:\Users\%user%\AppData\Roaming\r2modman\databases\Databases.db
• C:\Users\%user%\AppData\Roaming\r2modman\GPUCache\data_0
• C:\Users\%user%\AppData\Roaming\r2modman\GPUCache\data_1
• C:\Users\%user%\AppData\Roaming\r2modman\GPUCache\data_2
• C:\Users\%user%\AppData\Roaming\r2modman\GPUCache\data_3
• C:\Users\%user%\AppData\Roaming\r2modman\GPUCache\index
• C:\Users\%user%\AppData\Roaming\r2modman\IndexedDB\file__0.indexeddb.leveldb\000003.log
• C:\Users\%user%\AppData\Roaming\r2modman\IndexedDB\file__0.indexeddb.leveldb\CURRENT
• C:\Users\%user%\AppData\Roaming\r2modman\IndexedDB\file__0.indexeddb.leveldb\LOCK
• C:\Users\%user%\AppData\Roaming\r2modman\IndexedDB\file__0.indexeddb.leveldb\LOG
• C:\Users\%user%\AppData\Roaming\r2modman\IndexedDB\file__0.indexeddb.leveldb\MANIFEST-000001
• C:\Users\%user%\AppData\Roaming\r2modman\Local Storage\leveldb\000003.log
• C:\Users\%user%\AppData\Roaming\r2modman\Local Storage\leveldb\CURRENT
• C:\Users\%user%\AppData\Roaming\r2modman\Local Storage\leveldb\LOCK
• C:\Users\%user%\AppData\Roaming\r2modman\Local Storage\leveldb\LOG
• C:\Users\%user%\AppData\Roaming\r2modman\Local Storage\leveldb\MANIFEST-000001
• C:\Users\%user%\AppData\Roaming\r2modman\Network Persistent State
• C:\Users\%user%\AppData\Roaming\r2modman\Preferences
• C:\Users\%user%\AppData\Roaming\r2modman\QuotaManager
• C:\Users\%user%\AppData\Roaming\r2modman\Session Storage\000003.log
• C:\Users\%user%\AppData\Roaming\r2modman\Session Storage\CURRENT
• C:\Users\%user%\AppData\Roaming\r2modman\Session Storage\LOCK
• C:\Users\%user%\AppData\Roaming\r2modman\Session Storage\LOG
• C:\Users\%user%\AppData\Roaming\r2modman\Session Storage\MANIFEST-000001
• C:\Users\%user%\AppData\Roaming\r2modman\TransportSecurity

Registry keys:

• HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall\ac231ef6-6414-5f8d-b36f-3b57705721dd
• HKEY_LOCAL_MACHINE\Software\Microsoft\RADAR\HeapLeakDetection\DiagnosedApplications\r2modman.exe

How to erase r2modman 3.1.48 from your PC with the help of Advanced Uninstaller PRO

r2modman 3.1.48 is an application marketed by ebkr. Some people want to remove this application. Sometimes this can be difficult because removing this by hand requires some know-how related to removing Windows applications by hand. The best QUICK procedure to remove r2modman 3.1.48 is to use Advanced Uninstaller PRO. Here is how to do this:





1. If you don't have Advanced Uninstaller PRO on your system, install it. This is a good step because Advanced Uninstaller PRO is the best uninstaller and general utility to maximize the performance of your system.

DOWNLOAD NOW

• navigate to Download Link
• download the program by clicking on the green DOWNLOAD NOW button
• install Advanced Uninstaller PRO

2. Run Advanced Uninstaller PRO. Take your time to admire the program's interface and number of tools available. Advanced Uninstaller PRO is a very good Windows tool.

3. Press the General Tools category


4. Click on the Uninstall Programs button


5. All the programs installed on the computer will appear

6. Scroll the list of programs until you find r2modman 3.1.48 or simply activate the Search field and type in "r2modman 3.1.48". If it is installed on your PC the r2modman 3.1.48 app will be found very quickly. After you select r2modman 3.1.48 in the list of programs, some information regarding the program is available to you:

• Safety rating (in the lower left corner). This explains the opinion other people have regarding r2modman 3.1.48, ranging from "Highly recommended" to "Very dangerous".
• Opinions by other people - Press the Read reviews button.
• Technical information regarding the application you want to uninstall, by clicking on the Properties button.

7. Click the Uninstall button. A confirmation page will come up. accept the removal by clicking the Uninstall button. Advanced Uninstaller PRO will then uninstall r2modman 3.1.48.


8. After uninstalling r2modman 3.1.48, Advanced Uninstaller PRO will offer to run an additional cleanup. Click Next to go ahead with the cleanup. All the items of r2modman 3.1.48 which have been left behind will be found and you will be asked if you want to delete them. By removing r2modman 3.1.48 with Advanced Uninstaller PRO, you can be sure that no Windows registry items, files or folders are left behind on your computer.

Your Windows PC will remain clean, speedy and able to take on new tasks.

Disclaimer

The text above is not a recommendation to remove r2modman 3.1.48 by ebkr from your PC, nor are we saying that r2modman 3.1.48 by ebkr is not a good application. This text simply contains detailed instructions on how to remove r2modman 3.1.48 in case you decide this is what you want to do. Here you can find registry and disk entries that our application Advanced Uninstaller PRO discovered and classified as "leftovers" on other users' computers.