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-14T17:21:05+00:00

    thanks this worked

    You're commenting on a more than TWO YEARS old post, that is No Longer correct...

    Instead; REEEAD til the End of the Thread in the Forum, BEFORE posting nonsense, and thus confusing other people thanx!

    ( Sorry if that's harsh, but I'm SO fed up with people posting stuff that - any longer! - will NOT work... )

    ALL one has to do, is to change the Date = Year, to like 2017, on the config.xml (REEEAD back to find out Where it is located!), and then set the config.xml to be Read-Only, (REEEAD back to find out How!).

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-05-14T11:06:36+00:00

    thanks this worked

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-05-12T05:47:10+00:00

    It will not.

    Hello Anders,

    you're living in a notion that on February 1, powers have been put in place with the aim of destroying poor little config.xml. They have not, and that's including Windows Updates. If you think deeper about the matter, the problem we are dealing with is that a file, depending on regular renewal, suddenly is being left to itself, which is right the opposite of malicious attacks or any other way of getting touched. The threat to config.xml is no outside force, but time itself, and time only. You can test what I say here yourself by removing the read-only attribute for a while, waiting for the gadget to now fail again. I assure you that it won't, from personal experience. If there were any mechanisms left to automatically influence the date modified of config.xml, this discussion wouldn't exist, because the problem would not have arisen. The trouble isn't config.xml getting touched all the time. It's the file not getting touched all the time.

    Regards, VZ

    First you write:

    "The honor of coming up with the date fix clearly goes to Anders." on May 8, then you NOW write this quoted up here ?!

    WHAT is it you're saying by this your latest message?

    IF one sets config.xml's year to be eg 2017, and then ALSO set the same file to be Read-Only, it'll work until at least 2017, and by then we're all on Win10 or later, so the problem doesn't exist any longer.

    IF one ONLY change the Year to be eg 2017 (And not also sets config.xml to be Read-Only), then the next time you run Windows Update (MIGHT depend on what file it updates at the moment) the Weather Gadget won't work, again ...

    I have NOT touched MY config.xml since March 1, when i changed the year to 2017 and also set the file as Read-Only, and the Weather Gadget's still working just fine.

    Was this answer helpful?

    0 comments