I just updated my WLM to the final release and patched it. OneCare used to block my WLM once when I repatched my WLM with the new settings. It seems like OneCare remembers what the application is like and only allow that, perhaps. I tried manually adding the messenger to the allow list again and now OneCare says this cannot be done. -.-" Anyone has the same problem? Has anyone got a workaround for that?

what patch did you add? A-Patch?

Mess Patch. I was using A-patch, but I like the always on top button of Mess Patch more and Mess Patch has caught up with A-patch feature-wise.

does a-patch not muck up msn then?
messpatch stops my shared folders from working for some reason... (they never seem to synchronize, plus it says synchronization cannot occur at this time or something like that)

i use mess patch without problems

a-patch make some failure by sharing folders. he fix it as far as he can, he said

It seems like this is going to be a talk about A-patch vs. Mess patch for some reason... Well, can we go back on topic? Or... does any of you use Onecare?

To answer your questions, A-patch could get around with not disabling sharing fodler before Mess patch, but both no longer disable sharing folder now. That does not really relate to this though...

have the people don't fix this problem with onecare?
mess.be says, that he fixed the problem

at a-patch i don't know ^^

quote:

---

Originally posted by M73A
does a-patch not muck up msn then?
messpatch stops my shared folders from working for some reason... (they never seem to synchronize, plus it says synchronization cannot occur at this time or something like that)

---

And stay on subject next time

quote:

---

Originally posted by Stef
have the people don't fix this problem with onecare?
mess.be says, that he fixed the problem^^

---

According to the "warning" issued by MessPatch about OneCare, it doesn't seem compatible with it.

By user reports that I have seen, A-Patch has never had a problem with OneCare.

Having said that, I have no idea why one patch has a problem with OneCare and the other doesn't.

Edit: I've never used OneCare but maybe you could try deleting all the WLM entries after you've patched it, and then allow it when it asks you again.

@Ahmad: It seems like OneCare still remember it even if you deleted all the entry and that it checks if the application is modified somehow. I think it's probably file size. I'll try patching the new build of WLM before  it has connected to the internet first and see if that works, as OneCare detects builds too.

Looks like there's a new test version that might work for you.

http://forum.mess.be/index.php?showtopic=17641