Sign in   |  Join   |  Help
Untitled Page

ARCHIVED FORUM -- March 2012 to February 2022
READ ONLY FORUM

This is the second Archived Forum which was active between 1st March 2012 and 23rd February 2022

 

Beo6 Configurator driver blocked by Windows 10

rated by 0 users
This post has 9 Replies | 3 Followers

Mick3043
Not Ranked
Posts 13
OFFLINE
Bronze Member
Mick3043 Posted: Sat, May 2 2020 2:04 AM

Hi all,

 As I have observed some of you on here are using Windows 10 with the Configurator I was wondering if any had trouble with the driver being blocked by windows? The Beo6 shows connected, with the USB indication at the top of the screen, but I get the red cross over the white arrows at the top of the configurator window. And when I go into device manager the Beo5 line when clicked says this 'The driver for the device has been blocked from starting because it is known to have a problem with windows.' . I have tried it on 3 pc's (All running windows 10) with the same result. I am running version 6.84 of the configurator but also tried version 6.00 with the same result. I need to program the remote but are getting nowhere. Any ideas please?

Stoobietoo
Top 150 Contributor
Exeter, Devon, UK
Posts 692
OFFLINE
Gold Member

I had some trouble too to begin with. In the end I uninstalled the cofigurator using Revo Uninstaller so it cleared the program and any left behind files and entries. re-started my PC and I then re-installed the confiurator as Admin. I also run the program as Admin.

Do you have a Beo5 or Beo6? I ask because yoiu mention Beo6 then mention Beo5 when talking about the device manager.. A Beo5 will not work with 64bit versions of windows.

UPDATE - I have just put my Beo6 on the Config tool and it works perfectly. I look in Device Manger and it says Beo6. I have also put my Beo5 on and it does not connect showing the red cross. When I go into to Device Manager it shows Beo5 and says  - The driver for this device has been blocked from starting because it is known to have problems with Windows. Contact the hardware vendor for a new driver. (Code 48)

The Beo5 is not compatible with  64bit Windows and definitely not Windows 10. I have a virtual machine installed with Windows XP SP3 32bit and run that to program my Beo5. Your remote may be a Beo5 that has had the screen replaced at some time because they began using the Beo6 screens.

One way to tell if it is the Beo6 is that when you press the red dot button and center button the display will say Wireless at the bottom. If it is a Beo5 it does not have Wireless. (But this is not foolproof as I do not have a Beo5 with Beo6 screen to check).

Hope that helps

Stoobie

Mick3043
Not Ranked
Posts 13
OFFLINE
Bronze Member
Mick3043 replied on Mon, May 4 2020 12:21 AM

Thanks Stoobietoo. My remote is definitely a 6 . Before  I tried the configurator I was able to get the wireless menu item in the setup page. I will do as you suggested and use the uninstaller to get rid of all the configurator files and try installing again. Do you have V 6.84?

Stoobietoo
Top 150 Contributor
Exeter, Devon, UK
Posts 692
OFFLINE
Gold Member

Hi Mick,

I have some more information.

1. Is your Beo6 still working? Does the screen come on? Does it turn on when you place it in the charger connectd to the mains (not connected to PC as this is not powerful enough to charge).

2.  I have a second Beo6 that was corrupted, last month, by the Cofiguration Tool, when I tried to program it but the battery was not 100% charged. it used to work. Now it does not power up! (blank screen) I have tried it now also.

3. When I now put this corrupted Beo 6 on the tool I get the conformation sound from my PC that a USB item is plugged in, (but it does not power up as it should) I get the red cross( the symbol does not show it is connected unless the red cross goes away). When I look at Device manager is is showing as a Beo5 (not Beo6 which I know it is) and it has the same message you are getting. The driver for this device has been blocked from starting because it is known to have problems with Windows. Contact the hardware vendor for a new driver. (Code 48).

4. So I have a working Beo5 that connects to the tool and says Beo5 in the Device Manager when connected. A working Beo6 that connects to the tool and says Beo6 in the Device Manager when connected, and a non-working Beo6 that does not connect to the tool and says Beo5 in the Device Manager when connected.

You may have a more serious issue with your Beo6 but try a full re-install first.

There are posts with suggested solutions to the corrupted Beo6. The first time I tried it, 2 years ago, it worked. I bought a new battery and followed the instructions and it worked. It has not worked this time because I think I need a new battery again!

Thanks

Stoobie

 

Keith Saunders
Top 25 Contributor
Hampshire, United Kingdom
Posts 5,495
OFFLINE
Founder

You may wish to look HERE

Regards Keith....

Mick3043
Not Ranked
Posts 13
OFFLINE
Bronze Member
Mick3043 replied on Tue, May 5 2020 12:20 AM

Thanks for that Stoobie. Nice to know someone is having the same problem! :-).

 Yesterday I deleted the configurator and all its attached files. reinstalled it and the BEo6 connected. No driver problems. If you are talking about opening the Beo6 up and disconnecting the battery I have done that also. Not sure what that did if anything. I still have a very confused Beo6 though. Iset up the configurator for a Beosound5 and Beolab 4000 speakers and tried it in the simulator. The keys appeared to work, well, put out code anyway. So sent it to the Beo6. End result - None of the hard keys do anything. The screen shows the album covers and i can scroll through them and select one but thats as far as it goes. The volume ring seems to work but very slowly. Also the Beo6 ip is on the same network as the server but with a different last number. Would that be a problem?

Sorry to keep hassling you but I am getting a tad frustrated here. I printed out Hfat's guide which has helped but not totally I'm afraid.

 

Mick3043
Not Ranked
Posts 13
OFFLINE
Bronze Member

Sorry Stoobie, I didn't answer all your questions. 1/ Yes to all in #1

I still cannot turn on The Beosound5 using the remote by selecting the NMusic menu button, or the Nradio button. However I have found that once I turn the beosound on out of standby with my Beo4 remote ,(Which is about all that will do also - I got it when I purchased a Beocentre 2300), I can select which artist or Album I want to play. So a mixed bag all round.

 

Stoobietoo
Top 150 Contributor
Exeter, Devon, UK
Posts 692
OFFLINE
Gold Member

Hi Mick,

I'm sorry but I can't help further re your Beo6 as I use mine without wireless to control a Beosystem 3 and Beosound 9000.

At least you don't have driver issues now.

Good luck

Stoobie

Stoobietoo
Top 150 Contributor
Exeter, Devon, UK
Posts 692
OFFLINE
Gold Member

Hi Mick,

I was messing with my configuration today and thought I'd make a file with the BeoSound 5 and Beloab 4000. I don't know of you saw the box where you have to tell the remote how to send the signal for NMusic and NRadio.

In the configurator, go to the "Choose Products" tab, click in the BeoSound 5 picture then in the box below that you will see the "Sources" with a +

Click on that and you need to chose the correct option for NMusic then scroll down for NRadio. I don't know which is the option you need so you may need to try each one.

Be careful if you are trying lots of times that you do not run down the battery on your Beo6 or you may end up with the "dead remote" issue.

Stoobie

matador43
Top 75 Contributor
Posts 1,373
OFFLINE
Bronze Member
matador43 replied on Tue, May 19 2020 6:49 PM

Stoobietoo:

Be careful if you are trying lots of times that you do not run down the battery on your Beo6 or you may end up with the "dead remote" issue.

I believe that if you update your remote to the last firmware, it would not suffer that issue anymore! Maybe be weak on charge to the download process to complete but not look dead as it use to be with previous firmware.

 

Page 1 of 1 (10 items) | RSS