Hello,
I started looking into Instachecker Hotspot today and found that I was having some problems on my machine. I was unable to start Instacheck Hotspot. The initial error that I received was "Error HRESULT E_FAIL has been returned from a call to a COM component." (Please note that I am working with Windows 7)
With a follow-up error "Virtual Router Plus could not be started."
While going through troubleshooting this, I finally found a fix for it. The majority of the adjustments I went through were to enable services that run on your computer. There were a few other changes that I needed to go as well.
1.) You need to make sure you have is administrative rights on your PC to adjust these settings.
2.) Open services.msc in a run command or the search field in your start menu.
3.) Right-click on the following services. Select properties. Adjust the Startup type to Automatic.
5.) Right-click Local DTC. Located under Component Services > Computers > My Computer > Distributed Transaction Coordinator. Select Properties.
These are all the steps I had performed to fix the issue. I also want to explain why I went through these steps with referenced sites that can be reviewed if you want to check.
Step 3 was done because I traced the problem with a networking issue. It enables routing services for networking. I wanted to share a couple referenced sites I used:
Step 6 was used because it was the first step I found during the troubleshooting process in these forums.
Step 7 was used when going through the possible solutions to fix the problem with the Virtual Router. I looked for a route cause on Virtual Router Plus' website.
Step 8 was done based on additional reading up on forums and logical troubleshooting.
I wish you the best of luck fixing the issue.
~Manifestus
I started looking into Instachecker Hotspot today and found that I was having some problems on my machine. I was unable to start Instacheck Hotspot. The initial error that I received was "Error HRESULT E_FAIL has been returned from a call to a COM component." (Please note that I am working with Windows 7)
With a follow-up error "Virtual Router Plus could not be started."
While going through troubleshooting this, I finally found a fix for it. The majority of the adjustments I went through were to enable services that run on your computer. There were a few other changes that I needed to go as well.
1.) You need to make sure you have is administrative rights on your PC to adjust these settings.
2.) Open services.msc in a run command or the search field in your start menu.
3.) Right-click on the following services. Select properties. Adjust the Startup type to Automatic.
- Application Layer Gateway Service
- Internet Connection Sharing (ICS)
- Network Connections
- Network Location Awareness (NLA)
- Plug And Play
- Remote Access Auto Connection Manager
- Remote Access Connection Manager
- Remote Procedure Call (RPC)
- Routing and Remote Access
- Telephony
- Windows Firewall
5.) Right-click Local DTC. Located under Component Services > Computers > My Computer > Distributed Transaction Coordinator. Select Properties.
a.) Navigate to the Security tab.
b.) Check the first check box Network DTC Access.
c.) Within the Transaction Manager Communication section, check Allow Inbound and Allow Outbound check boxes.
d.) Select the last option in the Transaction Manager Communication section, No Authentication Required.
e.) Apply these changes.
6.) Open a command prompt window by typing cmd in a run command prompt or in the search field within the start menu. (This step is suggested in other posts.)b.) Check the first check box Network DTC Access.
c.) Within the Transaction Manager Communication section, check Allow Inbound and Allow Outbound check boxes.
d.) Select the last option in the Transaction Manager Communication section, No Authentication Required.
e.) Apply these changes.
a.) Type in the command "netsh wlan set hostednetwork mode=allow".
7.) I also disabled IPv6. (This may come back to bite you, but IPv4 will be around for a long time and you will more than likely not need it before you replace your current computer.) Open Registry Edit by typing regedit in a run command or the search field in your Start menu.
a.) Navigate to the following directory going through the directory tree on the left-hand side, HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ services \ TCPIP6 \ Parameters.
b.) Double-click EnableICSIPv6 and change the Value Data to 0.
c.) Press OK.
d.) Right-click the background in the right side of the Registry Editor. Select New and choose DWORD (32 bit) Value.
e.) Change the new entry to DisabledComponents.
f.) Open the new entry. Change the Value Data to FFFFFFFF.
8.) Navigate to your network adapters in the Windows Control Panel. Go through your Start menu. Select Network and Internet. Select Network and Sharing Center. Choose the Change adapter settings in the left column of the window.b.) Double-click EnableICSIPv6 and change the Value Data to 0.
c.) Press OK.
d.) Right-click the background in the right side of the Registry Editor. Select New and choose DWORD (32 bit) Value.
e.) Change the new entry to DisabledComponents.
f.) Open the new entry. Change the Value Data to FFFFFFFF.
a.) Right-Click on the network device providing your internet. It is probably your Local Area Connection. Select Properties.
b.) Select the Sharing tab.
c.) Check the first check box "Allow other network users to connect through this computer's Internet conection".
d.) Select your Wireless Network Connection.
e.) Open the Settings button located in this tab.
f.) I enabled all but the Remote Desktop service.
===========================================b.) Select the Sharing tab.
c.) Check the first check box "Allow other network users to connect through this computer's Internet conection".
d.) Select your Wireless Network Connection.
e.) Open the Settings button located in this tab.
f.) I enabled all but the Remote Desktop service.
These are all the steps I had performed to fix the issue. I also want to explain why I went through these steps with referenced sites that can be reviewed if you want to check.
Step 3 was done because I traced the problem with a networking issue. It enables routing services for networking. I wanted to share a couple referenced sites I used:
- Microsoft KB referenced because of a DHCP conflict I found in my Windows system logs.
- Microsoft Forum
Step 6 was used because it was the first step I found during the troubleshooting process in these forums.
Step 7 was used when going through the possible solutions to fix the problem with the Virtual Router. I looked for a route cause on Virtual Router Plus' website.
Step 8 was done based on additional reading up on forums and logical troubleshooting.
I wish you the best of luck fixing the issue.
~Manifestus
Last edited:
