Mathwiz Posted January 3, 2022 Share Posted January 3, 2022 Drifting a bit further off-topic, but he piqued my curiosity: 40 minutes ago, VistaLover said: The breakage is due to JS scripts that are not palatable to the web engines that can be used on Windows XP/Vista... I followed @VistaLover's instructions and the troublesome page now works on 360EE v13.0, along with the promised nag: So JS is clearly the problem (and NoScript is looking like the probable reason for @luweitest's success) but 360EE v13.0 is based on Chromium 86, which I'm quite sure is newer than the oldest version of that particular page, archived on Aug. 2017! So I tried the page again, in honest-to-goodness M$ Edge on honest-to-goodness Win 7, and it's broken there too! Well, at least it isn't specific to XP/Vista, but what the heck are they doing (or trying to do) anyway? I still suspect M$ sneaked some JS onto their pages that they knew would cause them to break on the Wayback Machine. (Gees, wouldn't it have been easier to have just used robots.txt?) Luckily only 19 scripts blocked on the oldest version, so time to start searching for the "bad" one.... ... and the winning uBO filter is: ||web.archive.org/web/*js_/https://support.microsoft.com/app/content/bundles/application$script,domain=web.archive.org (I changed the date stamp to an * so that - hopefully - this uBO filter will work on other M$ KB pages with this issue.) 2 Link to comment Share on other sites More sharing options...
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!Register a new account
Already have an account? Sign in here.Sign In Now