Spyware Sucks : Internet Explorer 7, Technology

FIX: msfeedssync.exe crashes (RSS synchronization - IE7 and IE8)

sandi — Thu, 31 Jul 2008 02:02:46 GMT

I have over 400 RSS Feed subscriptions that I keep an eye on, and which need to be checked regularly, sometimes every 15 minutes. A couple of days ago, msfeedssync started crashing every time a synchronization was due. The errors were:

Faulting application msfeedssync.exe, version 8.0.6001.17184, time stamp 0x47ccc712, faulting module msfeeds.dll, version 8.0.6001.17184, time stamp 0x47ccc720, exception code 0xc00000fd, fault offset 0x00002046, process id 0x1c98, application start time 0x01c8f1484814c945.

Faulting application msfeedssync.exe, version 8.0.6001.17184, time stamp 0x47ccc712, faulting module msvcrt.dll, version 7.0.6000.16386, time stamp 0x4549bd61, exception code 0xc00000fd, fault offset 0x00009bb2, process id 0x1ec0, application start time 0x01c8f1471a9905e9.

Faulting application msfeedssync.exe, version 8.0.6001.17184, time stamp 0x47ccc712, faulting module WININET.dll, version 8.0.6001.17509, time stamp 0x481c0708, exception code 0xc00000fd, fault offset 0x00004062, process id 0x2604, application start time 0x01c8f146dc893df3.

Faulting application msfeedssync.exe, version 8.0.6001.17184, time stamp 0x47ccc7a5, faulting module kernel32.dll, version 6.0.6000.16386, time stamp 0x4549d328, exception code 0xc00000fd, fault offset 0x0000000000037b93, process id 0xe94, application start time 0x01c8efbadb2c6b9a.

Faulting application msfeedssync.exe, version 8.0.6001.17184, time stamp 0x47ccc7a5, faulting module ntdll.dll, version 6.0.6000.16386, time stamp 0x4549d372, exception code 0xc00000fd, fault offset 0x00000000000529c5, process id 0x10f4, application start time 0x01c8ef973bc855f2.

As you can see, things were a real mess. These are the troubleshooting and diagnostic steps that I used to solve the problem:

Check if the Feed Task is corrupt by running the following command:

schtasks /query | findstr /i "user_feed"

Results:
User_Feed_Synchronization-{C73963F9-62BB-4 27/07/2008 10:15:00 Could not start

Ok, that is not good.
Stop and restart the Feeds Task:

C:\Windows\system32>msfeedssync disable
C:\Windows\system32>msfeedssync enable
Check Feed Task status again:

schtasks /query | findstr /i "user_feed"

Results:
User_Feed_Synchronization-{B70B1824-595E-4 27/07/2008 10:14:00 Ready
User_Feed_Synchronization-{C73963F9-62BB-4 27/07/2008 10:15:00 Could not start

Ok, not good - now I have two tasks - there is definitely an issue with the original task which is unable to start.
Disable the Feeds Task:

msfeedssync disable
Check to make sure that both Feed Tasks are gone:

schtasks /query | findstr /i "user_feed"

Results:
No tasks running - that is good
Restart the Feeds Task and check to see what we have got:

msfeedssync enable

schtasks /query | findstr /i "user_feed"

Results:
User_Feed_Synchronization-{B70B1824-595E-4 27/07/2008 10:23:00 Ready

Ok, this is good.. the bad Feed Task is gone, but msfeedssync is still crashing - something else is wrong.

Tried disabling Antivirus - that didn't fix the problem.
Tried running IE in "no add-ons" mode - msfeedssync is still crashing.
I fired up Fiddler, which records RSS activity. It turns out msfeedssync was crashing on the same feed every time - I deleted that feed but the subscription was cached somewhere that wasn't updating properly because IE8 continued to check the same feed despite it being deleted (and IE shut down and restarted, and the computer being restarted as well).
Ok, the fact that IE continues to check a feed that I have deleted from my Feeds subscriptions indicates that we are most likely dealing with a corrupt file, but which one?

I exported my list of feeds to an OPML file, then deleted the file "FeedsStore.feedsdb-ms" that is located in \Users\%username%\AppData\Local\Microsoft\Feeds. Next, I ran "msfeedssync forcesync".

Results:
msfeedssync continued to crash, but now it was crashing immediately instead of when it hit a particular feed :o( Ok, I just made things worse.
Using Process Monitor, I could see that msfeedssync was crashing immediately after it (apparently successfully) closed this file:

\USERS\%username%\AppData\Local\Microsoft \Feeds Cache\index.dat

I deleted the entire contents of that folder, including index.dat.

Results:
msfeedssync stopped crashing - YAY!!

Process Monitor is a free Sysinternals program available from Microsoft. You can download it here:
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx?PHPSESSID=d926

EOLAS: important changes soon

sandi — Thu, 08 Nov 2007 22:54:00 GMT

Well well well, isn't this interesting.

Microsoft have licensed the technologies that are covered by the infamous Eolas patent, and will be removing the “click to activate” requirement in Internet Explorer.

Regular readers of this blog will remember that a recent US High Court decision cast doubt on whether the original award to EOLAS of $521 would stand. The potential was there for the award to be reduced to $187 million.

The change that has now been announced by the IE team will require no modifications to existing webpages, and no new actions for developers creating new pages. IE will revert to its original behaviour.

There will be a "preview release" incorporating the changes called the "Internet Explorer Automatic Component Activation Preview", which will be available in December 2007 via the Microsoft Download Center. The change will also be made part of the next pre-release versions of Windows Vista SP1 and Windows XP SP3. It is anticipated that the change will be released to the general public as part of IE's April 2008 Cumulative Update.

Announcement: http://blogs.msdn.com/ie/archive/2007/11/08/ie-automatic-component-activation-changes-to-ie-activex-update.aspx

Revisiting the mystery user agent string IEMB3

sandi — Fri, 07 Sep 2007 00:23:00 GMT

Originally mentioned here , we have been unable to identify what is generating the UAS "IEMB3". If anybody knows, can you please reply to this entry? To repeat the original question: A User agent String (UAS) is made up of various segments that...(read more)

Google Desktop causing problems

sandi — Tue, 21 Aug 2007 00:03:00 GMT

Here is today's email question: "Dear Sandi, I would really appreciate your help. I've been trying for ages to find out what is wrong with my IE7 but there doesn't seem to be anything useful on the internet that I can find... Whenever...(read more)

Updated IE VPC images have been released

sandi — Mon, 20 Aug 2007 23:54:00 GMT

You can now download a free image of XPSP2 with IE6 or XPSP2 with IE7 installed at the link below - the images will expire on 7 December 2007: http://www.microsoft.com/downloads/details.aspx?FamilyId=21EABB90-958F-4B64-B5F1-73D0A413C8EF&displaylang...(read more)

Fix: display issue affecting IE7 and autoselect

sandi — Tue, 17 Jul 2007 00:32:00 GMT

I received the following email from a reader:

"I had an interesting email a few days ago from an IE7 user. He visited www.tigardchurch.org to find most of the text on the Home Page surrounded by “b’s”. I don’t own the site however; my wife is involved with keeping it current. I tested everything from: IE6, Mozilla Firefox to Adobe Safari and it all looked fine. I have held off loading IE7 for 1 yr after release and advised my clients to do so as well. Have you encountered this issue before?"

First of all, I argue strongly against recommending that people stay away from IE7 for "1 yr after release" unless there is a definite reason for deferring installation - that is, there is a line of business application that breaks, or an important Web site affected that you *must* be able to access, and even then I would consider it wiser to install an alternative Browser so that you can view the affected site rather than run the risk of continued exposure to the security exploits that affect IE6 and earlier and do NOT affect IE7. Of course, if a line of business application breaks, then that is something that may force you to defer installing IE7 until the application's vendor resolves the issue.

IE7 includes security updates and improvements that are simply too important to forgo without a good reason - IE7 has been immune to virtually every exploit that has affected IE6. Then there is the Phishing Filter, and Extended Validation Certificate support, and the Add-on Manager. Please don't hold off installing "just in case" or impose a stay-away timeframe.

Now, on to the Web site issues. I have been able to reproduce display problems for the site simply by toggling "Autoselect" under IE7's encoding options (tap the alt key on your keyboard if the Menu Bar is not enabled, then select View, then Encoding. You can turn off Autoselect there.

When I turn on Autoselect the page immediate refreshs and exhibits problems. When I turn off Autoselect and force a refresh of the page, the problem goes away. Examples below:

Without autoselect:

With autoselect:

Without autoselect:

With autoselect:

Unfortunately I simply don't know enough about Web page design and coding to be able to tell you how to fix this. Quick and dirty fix is to advise visitors NOT to enable the Autoselect encoding option, but the site's owners should also have a chat to somebody wiser than me about how to fix the issue, and whether the issue is with IE7 or the site itself.

Iframes / objects can apparently bypass phishing protection in Firefox 2.0.0.3 and Opera 9.10 - IE7 is unaffected

sandi — Thu, 29 Mar 2007 00:10:00 GMT

As reported on bugtraq@securityfocus.com by "nsp", Firefox 2.0.0.3 and Opera 9.10 apparently fail to detect a phishing site if it is embeded in an IFRAME / OBJECT label:

Demonstration pages can be seen here (warning, the URLs will prompt to install a Chinese language pack - there is no need to install the language pack):

http://zonafirefox.googlepages.com/prueba.html (using Javascript to create an iframe object)

http://zonafirefox.googlepages.com/prueba2.html (without Javascript)

The author of the email, nsp, states:

"Also, the following code can be used to bypass the phishing protection:

"<object type="text/html" classid="(phishing site)" data="(phishing site)"></object>"

The tests were realized using several many sites from Phishtank database. IE7 has no problems."

As a reminder, other problems with the Firefox phishing filter were revealed when it was reported back in February that the Firefox Phishing Filter can be disasbled simply by adding an extra slash after the domain suffix:
http://msmvps.com/blogs/spywaresucks/archive/2007/02/12/570602.aspx

According to Bugzilla, the "fix" for the backslash problem is something that needs to be done at Google's end. I note that there is discussion saying that things should be changed, but nothing to say that it has be changed, so I downloaded Firefox 2.0.0.1 to see what the situation is. Sure enough, the problem continues, so why was the bug closed as "resolved fixed"?

MSXML4 to be disabled in late 2007

sandi — Wed, 21 Mar 2007 21:11:00 GMT

MS are going to push out an IE specific kill-bit for MSXML4 in October. More information here:
http://blogs.msdn.com/xmlteam/archive/2007/03/12/msxml4-is-going-to-be-kill-bit-ed.aspx

Key changes:
http://blogs.msdn.com/xmlteam/archive/2007/03/12/upgrading-to-msxml-6-0.aspx

IE7 and "shrink to fit" problems - emails printing very small - hotfix released

sandi — Sun, 18 Mar 2007 00:12:00 GMT

A hotfix has been released by Microsoft to the QFE branch (Quick Fix Engineering) that fixes the infamous "shrink to fit" issue that some customers are experiencing after they install IE7. Basically, when affected users try to print an email it is printed in extremely small font and is completely unreadable.

The hotfix is "by request" for the time being. I am unable to advise when it will be released for general distribution.

The associated Knowledgebase article, being KB 932538, is not live as at time of publication.

If you have been affected by the shrink to fit problem, you will need to contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support

Note: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

IMPORTANT INFORMATION

What is the QFE branch, why is this important, and why should I only install a hotfix if it is absolutely necessary?

There are two development environments at Microsoft, being General Distribution Releases (GDR) and Quick Fix Engineering (QFE).

QFE branch releases are cumulative hotfixes that have been issued by Microsoft Product Support Services to address specific customer issues. QFE releases do not get the same quality of testing as the GDR branch. Please keep this fact in mind when deciding whether you will install the QFE fix for the shrink to fit issue.

I don't want to install the Hotfix but need to fix the shrink to fit problem. What can I do until the fix hits general release?

lf your emails are causing a problem for recipients, have a close look at your email header or footer because that is often the cause of the problem. Now, I'm not sure I can explain this properly, but my understanding of what is often happening is that very long headers or footers, if incorrectly formatted, will not "wrap" properly, and IE's shrink to fit engine will try to shrink the resulting long, unbreakable, string of text enough to allow it to fit on to the page. The shrink to fit engine cannot selectively shrink some bits of text more than others, so if you have one line (that long header or footer) that is a problem, the *entire* print job will be shrunk by the same amount, leading to the tiny fonts that people see.

A point of interest is that such a failure of text to wrap to the page properly has been around for a long time; for example, newsgroup postings made using Outlook Express and Mime Quoted Printable formatting are notorious for failing to wrap properly in non-MS news readers. Xnews is a product that comes to mind - I have to enable the "Word Wrap" feature before newsgroup postings made using OE and MQP will wrap properly. I also see an occasional problem with emails when using my Webmail client (MailExpress).

If you are having problems with emails that are being received, forward them to youself (deleting any header or signature) and then print. If you can, view the message in plain text and print that way as well. A workaround that you can try if you need to preserve the original format, is print to PDF and then print the resulting PDF file - I'll admit, I have not tried that, but it occurs to me now that it just might work. If you do not have Adobe or NitroPDF that give you the ability to print to PDF, then there are many freeware PDFing products out there.

The email message header does not print when you try to print an email message by using either Microsoft Office Outlook 2003 or Microsoft Outlook Express - also related to Shrink to Fit
http://support.microsoft.com/default.aspx/kb/931657

Windows Server 2003 Service Pack 2 and IE7 - you do NOT need to uninstall under most circumstances

sandi — Thu, 15 Mar 2007 20:51:00 GMT

Ok, so a couple of days ago Windows Server 2003 Service Pack 2 hit Automatic Update, catching all of us by surprise. That's all well and good, and believe me the team has heard feedback from many areas about the lack of information about the upcoming release, but the biggest problem for many of us was that the Release Notes stated that IE7 must be uninstalled before SP2 could be loaded. I'm sure my readers understand the potential problem here, with many servers already having IE7 installed, and potentially set to automatically download and install the service pack. With visions of damaged servers dancing in my head, I let the SBS gang know that I was attending sessions with the IE team the next day, and I would find out the hows, whys and wherefores.

Yesterday I was able to question the IE team about the Release Notes, asking for information about what breaks if SP2 is installed over IE7, and how to fix things if IE7 is not removed first. Luckily the sessions were also attended by one of the Server PMs.

Anyway, to cut a long story short, after I asked for information about why the warning was in the Release Notes, information about exactly what would break if the warning was not heeded, and information about what to do if people did not remove IE7 before installing SP2, it was realised that the Release Notes were incorrect. The true situation is that if you are not in the scenario described in KB 932600, or you are not upgrading an Eval Win 2003 to SP2, you do not need to uninstall IE7. David Overton confirms this advice, and the Release Notes have been updated to remove the erroneous information.

Edit: There is also an entry on the IE team blog confirming that, in most cases, it is ok to install SP2 over IE7.

Vulnerability: Phishers can bypass the Firefox Phishing Filter very easily

sandi — Mon, 12 Feb 2007 10:51:00 GMT

This is far too easy; the Firefox Phishing Filter can be disasbled simply by adding an extra slash after the domain suffix.

Original advisory:
http://kaneda.bohater.net/security/20070111-firefox_2.0.0.1_bypass_phishing_protection.php

The discovery is on Bugzilla - a demonstration is mentioned in the comments. The URLs I tested with are two that are mentioned in the discussion being:

"http://222.173.145.98/.bankofamerica.com/sas/profile/step1.htm
triggers an alert

http://222.173.145.98/.bankofamerica.com//sas/profile/step1.htm
Does not trigger an alert"

Note this comment:

"Firefox is the only browser that fails with this, Opera's latest compilation has corrected this issue and IE is immune."

I can confirm that both of the above URLs trigger a phishing alert in Internet Explorer. Firefox 2.0.0.1 only flags the first URL as a phishing page.

According to Bugzilla, the "fix" is something that needs to be done at Google's end. I note that there is discussion saying that things should be changed, but nothing to say that it has be changed, so I downloaded Firefox 2.0.0.1 to see what the situation is. Sure enough, the problem continues, so why is the bug closed as "resolved fixed"?

How can we trust a phishing filter that can be bypassed so easily? The simple answer is that we cannot.

Verisign needs to sort out their site so that it works with their Extended Validation (High Assurance) Certificate

sandi — Mon, 05 Feb 2007 10:43:00 GMT

Let this be a lesson to those companies out there that are going to purchase an Extended Validation (EV) certificate - please make sure that your site is coded so that the EV will display. Extended validation certificates are not cheap, and you do not want to be forking out money for an EV, only to have it fail to display.

Take the following example - I did not realise that Verisign was using an Extended Validation Certificate, and will explain why.

Verisign issued the EV certificates used by Paypal and Ebay. Let's have a look at some further information about these new certificates by clicking on the View Certificates option if we click next to the lock icon:

When we view the certificate details we see this:

Let's have a look at the Issuer Statement. Clicking that button opens an Internet Explorer window, and a Verisign page. The Address Bar is green when the Verisign page first opens, but it does not stay that way. Several of the screenshots in this article are taken using XP, but the problem also exists in Windows Vista.

This is the window that opens when we click on the Issuer Statement button:

When the Verisign page opens, we see a dialogue box asking for permission to display nonsecure items, and therein lies the problem. That dialogue box appears when Internet Explorer is set to "prompt" before displaying what is called mixed content, which is the default setting for IE7. In this case, Verisign has a secure (https) page that is displaying content (graphics) that is not a part of the secure page, instead being pulled from another area (sometimes called hot linking, or inline linking), thereby triggering the dialogue box. If we select "yes" and allow IE to display the non-secure content, the green Address Bar disappears. If we select "no", the green Address Bar stays, as you can see from the shots below. The only fix from the user's point of view is to set Internet Explorer 7 to never display mixed content, which some will say is a good idea for security reasons, but the fact of the matter is that Web sites need to make sure that their expensive Extended Validation certificates work when Internet Explorer 7 is being used with its default settings.

A Knowledge Base article that explains one of the ways that a Web page with frames may trigger the dialogue box can be found here:
http://support.microsoft.com/kb/184960

The equivalent SecureTrust "Issuer Statement" page that is reached in the same way when we visit a site that is using a certificate issued by SecureTrust, does NOT have this problem. Well done SecureTrust. I wonder if it was luck, or if SecureTrust knew there would be a problem if their page had mixed content.

I'll be reporting what I have found to the Internet Explorer team to see what they say; I suspect the behaviour will be "by design" because it pretty much guarantees that all content on an EV protected site is actually hosted by that site.

Here are screenshots of what happened on the Verisign page.

We say yes to displaying mixed content - the green bar disappears:

We say no to displaying mixed content - the green bar stays:

Exchange System Manager and IE7 and ESM's version of PSAPI.DLL don't mix

sandi — Sun, 04 Feb 2007 03:23:00 GMT

I'm sure I've written about this before - yep, I've got info up on www.ie-vista.com on the Knowledge Base page:
http://www.ie-vista.com/known_issues.html#tpa

The official SBS Blog have posted an entry about a problem with Exchange System Manager and IE7 here, complete with screenshots:
http://blogs.technet.com/sbs/archive/2007/02/02/esm-with-ie7-unable-to-open-the-help-file.aspx

Note that ESM is not the only product that has caused problems by installing its own copy of PSAPI.DLL. The fix is always the same - remove the copy that was installed by the software.

Other products causing problems by installing a second copy of PSAPI.DLL include McAfee software, BT Broadband Help (BT Yahoo Help), Motive SmartBridge, Hal Screen Reader and Supernova Reader Magnifier by Dolphin.

What I want to know is, why do those products install a second copy of PSAPI.DLL when the pre-existing copy in ..\windows\system32 works just fine.

Windows Vista - security updates available via Windows Update and WSUS

sandi — Tue, 30 Jan 2007 11:33:00 GMT

Microsoft have released a series of updates for Windows Vista, both x86 and x64 versions, including (finally) a phishing filter update for IE7 that speeds up Web surfing - the XP version of the phishing filter update was released a while back.

Here's what you will see in a corporate environment if you are using WSUS:

If updates have already been downloaded by your Vista system, or if Windows Update is otherwise active (installing or waiting for a reboot) you will see this icon in the system tray:

Vista users can access Windows Update easily, by clicking on the Start button and typing Windows Update:

Windows Update will show you what updates are available and away you go - you can install the whole lot or pick and choose - unfortunately, Windows Vista may need a reboot after installation (I thought we weren't going to have to do that anymore?) and I recommend that you check for further updates after you reboot - my system detected 3 updates on the first run, and another 5 on the second run. The reboot is a bit disconcerting the first time you see it; the system shuts down normally, then the blue/green loading screen comes up as per normal to let you know that the updates are being installed but then, be warned, your screen may go black again when the system restarts a second time as part of the update installation - it can be a bit scary to see the screen go black again - I actually thought something had gone wrong - but hang in there - if the power is still and there is hard drive activity things should be fine - be patient with lower resource systems.

When installation is finished you can View update history which has a cool feature - if you double click on any entry in Update History a new window will open just like this one that describes the update in detail:

Installed Updates window (see the failed ATI and Atheros updates? That's how the Ferrari 5000 was delivered to me - not too good Acer)

Updates detail window

Windows Update:

Selecting updates:

Updates successfully installed:

Playing with IE7 add-ons

sandi — Fri, 26 Jan 2007 12:12:00 GMT

I've been having a look at IE7 add-ins to use on my x64 Vista based system over the past few days. So far I've had a look at 3, all of which are available at http://www.enhanceie.com/, being Find As You Type, Feeds Plus and Feed Folder.

Feeds Plus has a competitor which has been around since 27 December 2006 called msfeedicon. I'll be having a look at that very soon and I suspect, going on what I can see on the developer's blog, that it may end up my preferred choice for beefing up RSS in IE7.

You can find the latest version of msfeedicon here - now at build 2.1:
http://www.wictorwilen.se/Post/msfeedicon-version-21-released.aspx

Version 2.0 - those using Vista may need to install this version if UAC causes a problem:
http://www.wictorwilen.se/Post/Announcing-msfeedicon-version-20.aspx

Remember, I am using Windows Vista on an x64 based system - problems that I see may not occur for you.

Find As You Type
This is a toolbar for IE and works by hooking Ctrl +F in Internet Explorer.

The advantages that I can see are that:

1) It works like the Microsoft Word Wheel, jumping through the web page to the first match as you type more characters
2) There are audio cues when you type a character combination that does not appear on the page

The primary disadvantage is that when we press Ctrl +F the previous Find entry is not highlighted for easy deleting.

Decision: This is a keeper for now.

Feed Folder
This add-on adds your RSS feeds to your Favorites list.

Strike 1 against Feed Folder: I don't use the Menu Bar within IE7, therefore the only place that Feed Folder would be of any use is in the Favorites Pane, but that did not work at all well.

Strike 2 against Feed Folder: Feed Folder crashed and displayed an "unspecified error" dialogue box if I tried to open an RSS group in the same way as I would open a Favorites Group, by clicking on the group arrow to display one feed in each window - according to Event Viewer, ole32.dll was involved.

The blue arrow that crashes Feed Folder

Strike 3 against Feed Folder: I was not happy to discover that when Feed Folder is installed, the RSS pane in IE7's Favorite Centre appeared empty, meaning that if I left Feed Folder installed I would only be able to access my feeds using that add-on. As soon as I uninstalled Feed Folder the RSS Feed Pane worked properly again.

Decision: Sorry, but if an add-on tries to enforce a "my way or the highway" situation, that add-on will be removed. Feed Folder lasted only 5 minutes on my system.

Feeds Plus
Ok, this was a little more successful.

Documentation for Feeds Plus is sparse, and it displays several different icons in the system tray, but we have to guess what those icons are for.

This one appears when Feeds Plus is working, for example when updating Aggregate folders

I am not sure what this one with the gleam is; I thought it was to indicate a new feed, or new content in a feed, but it has only appeared once, when Feeds Plus was first installed.

The default icon which is there all the jolly time

Strike 1 against Feeds Plus: It is constantly marking feeds as having an unread article which turns out to be days, or weeks old - very irritating.

Strike 2 against Feeds Plus: Feeds Plus is meant to display an Outlook style notification whenever new feed content is available but on my system this notification only appears when my laptop is first turned on. There is no sign of the notifications for the rest of the day.

Feeds Plus takes a little getting used to. It adds a new feed entry, "* All %foldername% Items", to every folder, and a Feed called "* All items" that captures the content for all subscribed feeds. To review the content of each folder in Aggregate view, simply click on the "All %foldername% Items" entry for that folder. But, be warned, if you leave the aggregate view before reviewing all new content, and switch to another folder, and if IE7 is set to automatically mark a feed as read when viewed, all feeds in that folder will be marked as read at the same time. Also, if you click on the All %foldername% Items a second time, all items will be marked as read. All feeds in a folder will also be marked as read if you click on a hyperlink in an RSS article when using aggregate view.

We seem to have found a bug - see how the aggregate entry, "All Internet Security Items", is not bolded? It should be because, as we can see, one of the Secunia entries has unread content.

Feeds Plus has only three option windows - screenshots below:

Decision: Feeds Plus can stay, for now, but I suspect it will be replaced by msfeedicon.