Weather gadget not working- Cannot connect to service

Anonymous
2013-01-14T14:07:43+00:00

original title: Weather gadget not working !!

I have Windows 7 Ultimate 64 - bit and my weather gadget is not working, it is displaying a message "Cannot connect to service .

I have also tried by turning off firewall and antivirus but it still don't works for me .

Windows for home | Previous Windows versions | Accessibility

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2013-01-15T09:19:57+00:00

Update:

Microsoft has DISABLED the weather and currency gadgets via a recent Security Update, due to concerns over the vulnerability associated with these gadgets running on your computer. You can read more about it here: http://support.microsoft.com/kb/2719662 . Adjusting your computer's settings and all these other "suggestions" people are making, will NOT work. The function has been REMOVED from the operating system. It has also been removed from the Windows 8 operating system. There are "theorists" that either agree that there is a security issue within the gadgets or Microsoft just does not want to support gadgets (usually third party software) and thus, has disabled them in Windows 7 and eliminated them in Windows 8.

Thanks to DaveNYC for the Info. Spread the word because many people are facing this problem just like you.

Was this answer helpful?

200+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2015-05-29T15:03:04+00:00

To all having this problem, the following worked for me:

After eading all kind of solutions, I changed the config.xml file according instructions and then I got connected but only to my own location (in my case Amsterdam). Tried everything else, no results, till I only give the exact zip code for the place I like to see the weather in the search menu and guess it worked, then I did the same on my computer in Greece (via teamviewer) and there it worked as well.

I hope it will help you as good as it did for me.

Ron

Was this answer helpful?

200+ people found this answer helpful.
0 comments

632 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2015-05-24T15:56:32+00:00

    Something had changed the Date on the config.xml

    ALL people that did NOT set the config.xml as Read-Only had experienced the same thing back then

    NOTHING had changed the date on the config.xml. NOBODY that had not set the config.xml experienced the same thing. They just hadn't set the date to the future, and neither had you. YOU DON'T UNDERSTAND THE MECHANISM.  GO BACK TO PAGE 26 AND CORRECT THE DEAD WRONG INSTRUCTIONS YOU GAVE THERE. THEY MIGHT GET PEOPLE WHO REEEEEAD THE WHOLE THREAD IN TROUBLE. DON'T COME BACK BEFORE YOU EVEN ONCE TRIED WHAT YOU RECOMMENDED THERE.

    In case I forgot: You don't HAVE TO set config.xml to read-only, You CAN do it, if you want to more-than-fix the problem, but it's no more useful or essential than copying settings.ini.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-05-24T07:20:22+00:00

    Thanks for the information. Best wishes , sincerely Major Naeem Hussain

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-05-22T05:29:11+00:00

    The only fix essential is changing the file's date to the future. Forget about the read-only part. Nothing at all will happen if you leave this out. It doesn't work like that. Config.xml can't be made not work in a sense the read-only attribute would help against. Your refusal to accept this results from not fully understanding the background process, despite having had the proper idea for a solution.

    Regards, VZ

    How strange then that I Feb. 15, wrote this in some threads:

    "And exactly a Week ago I had to RE-save my config-xml file, and today I had to do the same again, so it seems it'll be a Weekly manouver from now on to RE-save the config.xml"

    Something had changed the Date on the config.xml, but on Feb. 19th I also wrote this in the same threads:

    "This morning I simply changed the Date on the config.xml, to 2017, and then set the Attribute READ ONLY on the file, and it's still working ..."

    ALL people that did NOT set the config.xml as Read-Only had experienced the same thing back then, so why NOT set config.xml as Read-Only when it doesn't do any harm ...  and the Weather Gadget is STILL Working!

    So ...

    Changing the Year on the config.xml to 2017

    and then setting it as a Read-Only file WILL

    make the Weather Gadget work again, That's it.

    ... still stands, and no further discussion about this is necessary!

    Your refusal of accepting this FACT is Preposterous!

    Was this answer helpful?

    0 comments