Win 10 Creator Edition breaks drivers?

[N9JIG]

My computer recently updated itself to the Creator Edition of Win 10 Pro (v1703). Before the update it worked fine.

Now I cannot get my Radar Box to work properly. When the splash screen appears it shows RB1 but then it reports that no hardware can be found. The green light is on on the box itself

I reinstalled the drivers and no joy. I downloaded the drivers again from the AirNav site and reinstalled them even though they are the same versions already installed.

When I start the application (6.01.001) it goes thru the motions, the splash screen reports the RB1 and when the program gets around to running it now tries to connect to the network and that icon is yellow. Since I am not a Network subscriber it should be red, but it just cycles thru the 30 second update protocol over and over.

Next I will try deleting the application and reinstalling it but I wanted to see if there was anything else I should try first.

[N9JIG]

Update:

Must be a Windows Creator Edition issue. I downloaded and reinstalled the application from the AirNav website and still no joy.

I then fired up my laptop that has an older version of Windows 10 (1607) and downloaded and installed it there, worked great!

[neroon79]

Have you tried to run ANRB.exe as administrator?

While ANRB.exe not running:

If the green LED is on and the blue LED is not flashing, the drivers are installed and correctly recognized/processed by WINDOWS. In that case the problem is usually not caused by driver issues.

This problem is connected to the follwing thread: http://www.airnavsystems.com/forum/index.php?topic=10031.msg182452#new

Ingo

[N9JIG]

Yes, I ran as Administrator and it didn't change anything.

The application sees the RadarBox, it identifies it on the splash screen but then reports no hardware in the application itself. It might be an application issue instead, I assumed it was a driver since that is what usually breaks with Windows updates.

I did see that other thread but since I am using the classic box it didn't really apply.

[neroon79]

Yes, your are right, thread name doesn't match, but on the other hand that thread already drifted to a point were your recently discovered problems were already suspected, so I decided to link them.

Too bad that the feared nightmares came true.

Ingo

[neroon79]

Have you contacted support with your problem?

Ingo

[N9JIG]

I haven't yet contacted Support, that is next on the list. I wanted to see if there was a fix already.

In reading the other thread I tried to see if it was perhaps a conflict between my RTL SDR's and the RadarBox. (See http://www.airnavsystems.com/forum/index.php?topic=9981.0). On the same computer I have 2 SDR's I use for other purposes and they were otherwise engaged when I started the RadarBox application. When I shut down the SDR application I then started the RadarBox application and it form the SDR (Labeled as "MicroRB") and it connected to it.

So this leaves me back to the drivers for the RadarBox. The application itself seems to be fine with Creator Edition (v1703) of Windows but the hardware doesn't, likely due to the driver.

[Runway 31]

I wonder why Ingo's box is working OK?

Alan

[neroon79]

As stated on the other thread, non of my classic boxes are operating under Win10 V1703, but I have a week off from work from June 12th onwards. So I'll bring my Win10 1703 Laptop to my classic RB stations to see if I have the same issues.

Well, the Laptop is already here but unfortunately the power adapter is still in Heidelberg, so unable to test it right now. On workdays there is no time for such things available. So it makes no sense to bring the box to Heidelberg.

Hopefully support can solve the problem earlier -well if it is solveable. Recently you don't no it for sure if it comes to Win10.

Ingo

[Runway 31]

Just noticed you are on 1067 Ingo.  I have advised support regarding the issue

Alan

[AirNav Support]

Is there anyone else other than N9JIG having issues?

Does the RadarBox show as connected in the driver menu in Windows?

[neroon79]

I'll try to test it tomorrow. Hopfully the energy cells will last long enough.

Ingo

[neroon79]

I couldn't wait any longer and checked my Win10 1703 Laptop. Diver installed, box recognized, software opened, aircraft on screen.

So no problem discovered with my installation.

Ingo

[Runway 31]

I have installed 1073 on my other laptop and will check it out with classic RB, RB Dongle and NuElec dongle to see how it goes

Alan

[N9JIG]

After reading Ingo's response that his works with 1703 I checked a couple other things.

First I uninstalled the RB via Device Manager and then using Add/Remove Programs and then deleted ALL AirNav application and files that I could find on the computer, then searched the Registry for any AirNav entries and deleted them. I then unplugged all other USB devices (2 SDR's, 14 USB-serial cables for radio receivers and the hubs that support them).

I then plugged the RadarBox back in. Windows installed drivers automatically and reported them as the best ones. I then downloaded and installed the RadarBox 6.01.001 application, installed it and tried it again. Still got the same results, the splash screen identified RB1 but the application reported the same No Hardware message and red box.

I then force-wrote the drivers from the AirNav downloads site and tried it again, still no joy.

I then unplugged the RB and plugged in an SDR, the SDR worked fine.

I can't understand the issue here if Ingo's install works and mine doesn't with the same version of Windows.

Ingo: What version of the RB application are you running? Could it be the application that is broken and not the drivers?