VB 4.3.18 breaks VPN connections on Win 8.1 x64

Discussions related to using VirtualBox on Windows hosts.
Post Reply
jimwillsher
Posts: 10
Joined: 16. Apr 2012, 08:38

VB 4.3.18 breaks VPN connections on Win 8.1 x64

Post by jimwillsher »

Windows 8.1 Pro, x64, 32GB RAM.

I've used many versions of VirtualBox, all without problems. I've just upgraded to 4.3.18 from 4.3.14 and now my PPTP VPN connections do not work. When I try to establish a connection, after about 60 seconds I get the "unknown error has occurred" message. Digging deeper, I see that Remote Access Connection Manager service cannot start due a "cannot find file" message.

Using System Restore to revert to 4.3.14, everything works correctly. Updating to 4.3.18 again straight after the restore, VPN connections fail again with the same symptoms.

So I have rolled back to 4.3.14 as it's working correctly.


Jim
micrarior
Posts: 1
Joined: 8. Mar 2015, 03:47

Re: VB 4.3.18 breaks VPN connections on Win 8.1 x64

Post by micrarior »

I have same problem
VB: 4.3.18.r96516
Windows: 8.1 x64
Avast Free: 2015.10.0.2208

After uninstalling or upgrading VB getting broken "Remote Access Connection Manager" and VPN connections don't work
Only recovering from restore point helps

Code: Select all

- <Event>
- <System>
  <Provider Name="RasMan" /> 
  <EventID Qualifiers="0">20030</EventID> 
  <Level>2</Level> 
  <Task>0</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2015-03-08T01:56:33.000000000Z" /> 
  <EventRecordID>28892</EventRecordID> 
  <Channel>System</Channel> 
  <Computer>hell</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>Не удается найти указанный файл.</Data> 
  <Binary>02000000</Binary> 
  </EventData>
  </Event>

Code: Select all

- <Event>
- <System>
  <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" /> 
  <EventID Qualifiers="49152">7023</EventID> 
  <Version>0</Version> 
  <Level>2</Level> 
  <Task>0</Task> 
  <Opcode>0</Opcode> 
  <Keywords>0x8080000000000000</Keywords> 
  <TimeCreated SystemTime="2015-03-08T01:56:33.163290000Z" /> 
  <EventRecordID>28893</EventRecordID> 
  <Correlation /> 
  <Execution ProcessID="652" ThreadID="1040" /> 
  <Channel>System</Channel> 
  <Computer>hell</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data Name="param1">Диспетчер подключений удаленного доступа</Data> 
  <Data Name="param2">%%2</Data> 
  <Binary>5200610073004D0061006E000000</Binary> 
  </EventData>
  </Event>
Attachments
device manager. driver error
device manager. driver error
Безымянный.png (32.05 KiB) Viewed 1155 times
karlt
Posts: 1
Joined: 20. Jul 2015, 03:59

Re: VB 4.3.18 breaks VPN connections on Win 8.1 x64

Post by karlt »

I just upgraded to VirtualBox 4.3.28 and I could no longer connect my Windows VPN connection. Am also using Windows 8.1.

Before upgrading VirtualBox my devices were fine:
1 devices-before-spx.JPG
1 devices-before-spx.JPG (104.09 KiB) Viewed 997 times
But then after upgrade VirtualBox and reboot my VPN didn't work, I had issues with the 'Secure Socket Tunneling Protocol Service' and 'Remote Access Connection Manager' and under Device Manager I have errors:
2 devices-after-VirtualBox4.3.28.JPG
2 devices-after-VirtualBox4.3.28.JPG (104.18 KiB) Viewed 997 times
Process: Uninstall the non-working miniport, reboot and when you create a VPN or try to connect, Windows will automatically reinstall the drivers.
The problem is Device Manager doesn’t let you uninstall the devices, so this is how I managed to fix it:

1. In Device Manager, right-click on the non-working miniport, choose Update Driver.
2. Choose Browse my computer.
3. In the next window, choose Let me pick driver from a list.
4. Uncheck Show compatible hardware. From the Manufacturer list, choose Microsoft, and from the Network Adapter list, choose Bluetooth Device(Personal Area Network). (It can be any device the user is allowed to uninstall.)
5. Back in the device manager, delete the device that just turned into a Bluetooth Device(Personal Area Network).
6. Reboot.
7. Delete your VPN information and then enter it again. (you may not need to do this step).

Hope this helps someone as I was at a loss for sometime to resolve this.

Cheers,
Karl
Post Reply