Windows 7 Backup fails saying it skipped files

Using Windows 7 built-in backup system with the automated settings is simple... sometimes too over-simple, and lacking for easy adjustment.

Certain programs you install create their own user account on Windows 7 (and Vista or XP I assume). In my case, I was working on a system that has two programs installed that Windows 7 Backup complains about, Logmein Remote support Software and Quickbooks (2010, 2011, 2012 are all the same I believe).

When the Windows 7 Backup runs, it completes, but gives you a system warning saying that it has failed since it wasn't able to backup certain files (listed below in my instance).

C:\Users\LogmeinRemoteUser\Contacts
C:\Users\LogmeinRemoteUser\Searches
C:\Users\QBDataServiceUser20\Contacts
C:\Users\QBDataServiceUser20\Searches
C:\Users\QBDataServiceUser22\Contacts
C:\Users\QBDataServiceUser22\Searches

The article I've linked to in the title had a response from someone mentioning a microsoft Knowledge base (KB) article:

http://support.microsoft.com/kb/979281

I used one of the Resolutions listed for Scenario 2, the 1st bullet point / resolution says:

- Create the missing LocalLow, Contacts, and Searches folders that are listed in the error message.

So I simply traversed to one folder below the folders listed in the error messages about files being skipping, and created new Empty folders with names that match the error message names (I had to provide / confirm administrative privileges to continue and take ownership to get into the folders).

I created new empty folders the same as the following:

C:\Users\LogmeinRemoteUser\Contacts
C:\Users\LogmeinRemoteUser\Searches
C:\Users\QBDataServiceUser20\Contacts
C:\Users\QBDataServiceUser20\Searches
C:\Users\QBDataServiceUser22\Contacts
C:\Users\QBDataServiceUser22\Searches

I then re-ran the backup and it didn't complain about files being skipped anymore, and now I can assume/presume that when (if ever) there actually is an error about a file being skipped, I will get the system warning message, and I will know there's a real problem instead of "ignoring" the warnings and never looking too closely since it used to warn after every backup saying the backup had either not finished successfully or had completed with errors (skipped files).