In reply to DeanP’s post on February 25, Sign up or log in Sign up using Google. If you attempt to uninstall WinDriver while there are open handles to the WinDriver service windrvr6. After file was overwritten with the older file. Uninstall the device using the wdreg utility:
|Date Added:||19 October 2005|
|File Size:||46.56 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
On a target PCon which you installed the Reove kernel module windrvr6. For me, neither Lab Tools What do you do? I assume that I did not sufficiently remove all the driver components to trick my PC to re-installing the drivers as though this was my 1st attempt.
Thank you for your quick response. I should have mentioned I am using Windows 10 and 64 bit software both Uninstall the device using the wdreg utility: Instead, I have only “WinDriver” under “Jungo”.
Jungo Connectivity Driver
Ratandeep and Ian, I will contact Atmel Tech support but in the interim, I was able to successfully get this hardware working on my laptop this morning. Close any windrifer that are using the WinDriver driver module. Home Questions Tags Users Unanswered. Sign up using Email and Password. There is no known issue with WinDriver that requires uninstalling and then re-installing it.
I appreciate your efforts.
Close any applications that are using the WinDriver driver modules. By default, WinDriver module names begin with windrvr6.
This section will help you to uninstall either the evaluation or registered version of Windrivee . This ensures that you do not uninstall the driver while it is being used. Ian Bakshan Replied on February 24, This site in other languages x. DeanP Replied on February 22, I would also suggest you to update chipset drivers of your computer from manufacturer’s website.
Uninstall the renamed driver using the OS’s kextunload utility: What exactly is Jungo WinDriver? Is the issue specific to this device?
ShieldSquare reCAPTCHA Page
In reply to Ratandeep’s post on February 22, I’m hoping someone can help. The PC that was not working had windrvr6. By default, WinDriver module names begin with windrvr6. Consult their website for more information.