I guarantee that the first time my phone hits on me I will be affected.

Based on other comments I don't doubt there is something broken about it. But for me, when mine went away I spent some time searching, trying to figure it out. Gave up and lived with it after a few minutes. Surfed /. for a few days in a row and magically it was back. Then I got busy, life and all that, and hadn't been to /. in months. When I finally came back the ads were back. A few days of consistent visits and one day the box was back and checking it removed the ads.

I chalked it up to a change that basically works like ( good karma + consistent visits = remove ads ). Have no idea if that's right, just the behaviour I observed. I can say, unlike other commenters, that if the box was there and I checked it then it worked and ads were removed. I typically surf /. with Firefox or Seamonkey fwiw.

Thanks for clearing that up for us Mitt!

Yes, thanks, I read another comment saying the same thing after I posted. I guess I was forgetting the whole replace only aspect of .net now. I don't use it a lot and back in the day you could sanely maintain multiple versions on the same system. So in my mind when reading the summary and skimming the article I was thinking this only referred to people specifically targeting the freshly released 4.6.

Here's hoping for a quick patch release. And, as also pointed out in other comments, if you are able the .Net git repository has the patch available for those who don't want to wait for the official release.

I don't know much about this but isn't it possible to just reduce the optimization level to avoid this behaviour? Sounds to me just skimming things that this the result of overly aggressive optimization. I know that's not a long term fix but is it a short term option until MS rolls out the patch?