Interesting - mine's grey too. It worked fine on XP64. This problem has only appeared with the move to W7 64 (same level drivers/GFConfig as XP).I see another thread over on SimFlight which sounds like the same problem, but they put it down to FSUIPC, which I don't use at all.Sounds like something not quite right with the 'grey' level hardware and W7. And with the GF site down now for quite a while, unlikely we will get that addressed.Unless someone is watching . . .

GF site is up for a couple of days now.i have only their throttle and it runs like a charme.only when fsx crashes it won't shut downwhen you installed the driver, did you turned UAC an AV off?then run it as admin john

Edited February 19, 201214 yr by starter

Thanks for the heads up on the GF site. I run with UAC permanently off. All tasks are run as admin. AV off for downloads. All my other GF modules work fine.Let me ask the question - is there anyone out there with a 'grey' GF46 that runs fine under W764 (preferably without FSUIPC) ?

Dick, you're probably not going to like the answer. I have 3 grey GF-46s and they all experienced the same issue as you report when I first got them. Then, for reasons unrelated to FSX, I reformatted and reinstalled W764. Since then, they have all worked like a charm, with one weird hiccough...when the machine is booted from cold (i.e. first thing in the morning) they are not recognised at all. I leave it 5 mins, either do some browsing, read the Avsim forum or make a coffee. Reboot it when it's warmed up and there they are. They then all work without issue for the duration of the session. My longest flight was ZSPD-KRFD - around 13 hours in the Level D, and they and all the other GoFlight stuff (total 20 units) were just fine.I can only conclude that something in W7 had become either corrupted or scrambled and the re-install fixed it. No idea what it was though. Might have been a USB driver??Cheers,Andy

Ouch. You're right, Andy, I don't like that answer ! I've only just finished migrating to W7 and gotten all my addons and tuning done, so I'm not about to go back and re-install !The thing is, once I'm into a flight, it <<seems>> to work OK, although at the moment as I'm in the final stages of tuning I'm doing lots of short flights and taking FSX up and down like a yo-yo, which isn't helping. My present workaround is to remove GFDevFSX from exe.xml and start it manually when I've got everything else (ASE, MCE, Shade, FSX) up and running. And just before I start GFDevFSX, I fire up GFConfig and make sure it can see the GF46. If it can't, then I replug it until it does. Life shouldn't be this complicated !I noted what you said about the cold start. It just so happens that where I fly is the coldest room in the house (which is great for CPU/GPU temps, but not for the pilot !) Now I don't suppose . . . . .I raised this with GF tech support and also put it up on their forum. They sent me the latest GF software (2.3) to try, but I'm not hopeful.

Just a quick update - installing GF software 2.3 did not fix the problem. Nor did disabling power management/suspension for the USB ports (in Device Manager and W7 Power Management), though I think these were all good things to try.What I have noticed on my setup is that the GF46 seems to run fine until I plug something else into the same hub. In my case I regularly use a spare slot in the same hub for a memory stick to transfer files, for no other reason than it is convenient. When I pull the memory stick, nine times out of ten the GF46 drops out next time I start FSX, and I have to plug it into another slot to get it working. So now my plan is to leave that hub alone ! And so far it seems to be working.

I'm having the same kind of issues with my GFTQ module (note, it's not the factory TQ but the Remote Mount Kit, and is connected to my real LJ45 throttles). I can sometimes come in and fire up the sim and the throttles work. Then other times (like right now, which lead me to this thread via searching for a solution) it doesnt. I've already rebooted once. I think we can conclude it's a USB issue, but I have to say that before I recently rebuilt my sim (hardware) I never experienced this.