There was an interesting article posted on the AutoPatcher.com Blog today that talks about the history and future of AutoPatcher.  They talk about the Blaster worm which spread like wildfire across the Internet and rendered many computers unusable until the infection was removed.  Here is a short excerpt from the AutoPatcher.com Blog:

We will be working on a web-oriented solution which we hope will give use two great benefits: easier and more efficient upgrades and easier “all-in-one” creation. Since I’m in the middle of exams, I will probably start coding in about a week from today. Although we can’t really provide an estimate on when the next AutoPatcher will be available, we will do our best to have everything ready (and above all Microsoft-free) just in time for an October release.

One of my experiences with the Blaster worm:

I remember the days of the Blaster worm well since I had to clean many computers infected with it (as well as some similar ones).  I remember one instance very well.  At the time some of the colleges around here were huge breeding grounds for computer viruses upon the arrival of new students.  My girlfriend (at that time) needed to have Windows XP reloaded on her computer.  I think it was because it was infected with the Blaster worm but I can’t remember for sure.  I grabbed the Windows XP SP1 CD, reformatted the hard drive, and reinstalled Windows.  Installing Windows XP SP2, all of the latest security updates, and Anti-Virus software were my top priorities after installing Windows.  However, I learned a lesson the hard way that day.  As those of you in the IT industry know Windows XP SP1 didn’t include the built-in firewall.  That important security feature came as part of the SP2 release.  The tiny problem was that I had left the network cable plugged into the computer when reinstalling Windows on a network with thousands of laptops owned by college kids.  Needless to say, a bunch of these computers didn’t have the latest security updates or current Anti-Virus programs installed which resulted in a bunch of computers on the network becoming infected.  Since I had the network cable plugged-in it didn’t take long for the fresh install of Windows XP SP1 to get infected with the Blaster worm even though I started installing SP2 almost immediately after reinstalling Windows.  To make a short story longer, I ended up reformatting the computer and reinstalling Windows XP again.  This time I was sure to unplug the network cable and install SP2 before plugging it back into the network.  That day I learned an important lesson:  install the latest security updates before connecting the computer to a network, especially one that you don’t manage yourself.  This is where I think AutoPatcher comes in really handy.  It allows you to get almost all of the latest security updates installed before connecting to the Internet.  Of course, now I usually slipstream SP2 into the Windows XP CD but AutoPatcher is still very useful because there have been a lot of updates released since SP2 came out. 

Windows Vista Service Pack 1 is targeted to be released in the first quarter of 2008.  Since the Vista SP1 and Windows Server 2008 engineering efforts are aligned they are also targeting the first quarter of 2008 for their release date.

Here is an excerpt talking about what changes SP1 includes:

In addition to updates we’ve previously released, SP1 will contain changes focused on addressing specific reliability and performance issues we’ve identified via customer feedback, supporting new types of hardware, and adding support for several emerging standards.  SP1 also makes additional improvements to the IT administration experience.  We didn’t design SP1 as a vehicle for releasing new features; however, some existing components do gain enhanced functionality in SP1.

See Also:

• Announcing Windows Vista Service Pack 1 Beta - Windows Vista Team Blog
• Windows Server 2008 Timing Update - Windows Server Division Weblog
• Windows Vista SP1 white paper

A tech community called Lunarsoft had a talk with a member of the Microsoft Team and found out the reason behind why AutoPatcher received the takedown notice. They also have another story about all the talk of why AutoPatcher got their takedown notice and people wanting to help.

More can be read at http://lunarsoft.net

read more | digg story

Other related Lunarsoft articles:

• AutoPatcher project receives takedown notice - Aug. 30
• [Exclusive] The reason behind the AutoPatcher takedown notice - Aug. 30
• More trouble for AutoPatcher and other projects? - Aug. 31
• AutoPatcher Ray of Hope? - Sept. 2

I just saw on the AutoPatcher Blog that Microsoft sent them a takedown notice requiring them to remove the download page from their website.  For those of you who don’t know what AutoPatcher is it is basically a compilation of Windows updates released since the most recent service pack.  On August 20th, 2007 they announced that they now had AutoPatcher releases for Microsoft Office XP/2003/2007 in addition to the standard Windows updates.

The nice thing about AutoPatcher was that it was a great time saver for computer technicians who work on multiple computers for clients.  It has saved me countless hours when updating computers for clients, which translates into increased savings and adds value to my services.  I still occasionally run into new clients who are still running Windows XP SP1 and even a few that don’t even have SP1 installed.  Even with all of the updates bundled into one file that you can download and burn onto a CD or DVD it still usually takes 1-2 hours to install all of the service packs and recommended updates.  That is without downloading the updates from the Internet on every single PC.  If I had to download all the updates from the Internet and the client was on dial-up it would take all night.  Even on high speed Internet it usually takes a little while to download the few hundred MBs of updates released since Windows XP SP2.  It is especially inefficient use of your time if you are onsite at a client’s office or house.

The other nice timesaving feature of AutoPatcher was the automated installer that installed all the patches one after another without prompting.  I would just select all the updates I wanted to install, click on start, and then work on something else for an hour or two and let it finish.  Microsoft Update basically does the same thing but it takes a lot longer since it needs to download the updates from the Internet before it installs them.

I must say I’m going to miss AutoPatcher and I hope Microsoft reconsiders their actions.  However, I was expecting this to happen for quite awhile and I doubt Microsoft will change it’s mind.  At least I have most of the latest AutoPatcher releases burned to a DVD and I will probably keep using them until they become obsolete.

I setup a brand new Dell Dimension E520 for one of my clients a few months ago.  It was running Windows Vista Ultimate Edition.  I got everything setup without a hitch until I tried to install AVG Free.  After I installed AVG I kept getting the following error when the computer started up as well as when I tried to double-click on the desktop icon to start AVG:

avgwb.dat - Application Error
The application failed to initialize properly (0xc0000022). Click OK to terminate the application.

I tried all kinds of things to try to troubleshoot the issue.  I uninstalled AVG and reinstalled it.  I right-clicked on the AVG icon and selected “Run as administrator” which prevented the error from coming up but wasn’t a permanent solution.  I contacted Dell technical support because it was a brand new computer and I figured the problem was caused by something Dell did when they configured UAC in Vista.  I even purchased AVG Anti-Malware Edition and contacted Grisoft’s technical support team (the free version doesn’t come with technical support).  However, nothing I tried seem to help.  I finally decided that I needed to find a temporary solution and revisit the problem after Grisoft’s technical support team had more time to analyze the problem.  Since the problem seemed to be a security related issue caused by UAC in Windows Vista I temporarily disabled the UAC.  That temporarily “fixed” the problem and got AVG working until I could find the cause of the problem and fix it.

The Grisoft technical support team never did find a solution for me and Dell wasn’t much help at all.  Apparently they were all as baffled as I was.  When I was looking at the computer again today I noticed that the AVG error was coming up again.  It looked like someone had enabled UAC since the last time I looked at the computer so I decided to take another crack at the issue.  When I figured out the solution I decided to post it on my blog to help other people troubleshoot similar problems and hopefully save them some of the frustration I experienced.

The Solution:

I already knew the problem had something to with the avgcc.exe program not being granted the proper security permissions to run.  I did a little more research on the Internet and decided to use Dependency Walker to try to figure out what files avgcc.exe was having trouble accessing.

1. I downloaded Dependency Walker and extracted it.
2. I ran Dependency Walker and opened the “C:\program files\Grisoft\AVG7\avgcc.exe” file with it.
3. At the bottom of the screen it told me there was an access denied error when trying to load the “C:\windows\system32\mfc71.dll” file it was dependant on.
4. I opened Windows Explorer and browsed to the MFC71.DLL file, right-clicked on it, and selected properties.
5. Then I clicked on the Security tab.  It gave me a UAC security warning about changing the permissions of system files and I clicked Continue.
6. I added the Everyone group and gave it Read/Execute access to the file.
7. I tested AVG and it was working just fine after that.
8. I went back in to check the settings of some similar files and it looked like the previous permissions had been correct.
9. I removed the Everyone group and tested AVG.  It still seemed to be working ok so I rebooted to double-check and everything came up just fine.

Conclusion:

It looks like the permissions for the MFC71.DLL file got corrupted somehow.  I don’t know if it was something wrong with Dell’s original setup or what caused the problem.  I haven’t ran into this problem on any other Dell computers running Vista yet.  If you have ran into the same problem before please post a comment and let me know.  I’d really appreciate the feedback.  Thanks!

A couple important Windows Vista updates were released recently to fix various performance issues.  There is more information, as well as links to download the updates, on David Overton’s Blog.  You must be running genuine Microsoft Windows to be able to download and install the updates.

See KB938194 and KB938979 for more information.

I was trying to update QuickBooks 2005 to R10 today and it kept getting stuck in the middle of the update process.  It turns out that all I had to do fix this problem was take the QuickBooks 2005 installation CD out of the computer before installing the update.

Any users (and from reading other forums, there seems to be a lot of them) that have a problem with the update utility stopping at 24% when trying to copy the file qbupdate.exe.LOCAL might try simply removing the installation CD form the drive. Noone tells you this, but after hours of searching forums, I found the solution. Simple, yet who would have thought of it? Anyway it worked for me, and if this doesnt work, search the forums for ‘update stop’, and several other solutions are listed, but this one is the simplest, so I thought I would leave a post about it.

Source: QB update utility stops working at 24%

I found a nice surprise in my Inbox this morning.  I went into an e-mail message that contained an Adobe Acrobat PDF file and clicked on the file to preview it like I normally would.  However, I happened to notice that it didn’t say Foxit PDF Preview Handler above the preview window anymore.  I wondered if Adobe had finally included an Outlook 2007 PDF Preview Handler in one of their recent software updates.  I did a little more research and found out that with the release of Adobe Acrobat/Reader 8.1 they did include a PDF Preview Handler for Outlook 2007.  Adobe’s version of the preview handler doesn’t seem to have as many features as the Foxit preview handler but it is still pretty decent.

More information on the Adobe 8.1 update:

• PDF Preview for Outlook 2007 via Adobe Acrobat Reader 8.1 Update
• PDF Preview Handler included with Adobe Acrobat 8.1
• New features and issues addressed in the Acrobat 8.1 Update - Adobe TechNote KB401730

Download Links:

• Adobe Reader 8.1 Download
• Adobe Acrobat 8.1 Professional/Standard Update 

If you would like to run Office 2003 and Office 2007 on the same computer I would highly recommend checking out the following tips from David Overton’s Blog:

• Installing Office 2003 and Office 2007 on the same system
• How to get rid of the installer / configuration dialog when running Office 2007 and Office 2003 on the same system - for Vista and other versions of Windows
• Information about using 2007 Office suites and programs on a computer that is running another version of Office (Microsoft KB928091)

I was just reading an interesting post on David Overton’s Blog talking about why small businesses should use Office 2007.  Here is a summary of the topics he covers in his post:

• For those with a version of Microsoft Office, but not 2007
  • More Professional and Impressive documents and materials
  • Customer Management
  • Mobile access to information
  • Greater Efficiency
  • Understand information better
• For those without a version of Microsoft Office - All of the above, plus
  • Document compatibility
  • Suite that has tools for 21st century
  • Access to thousands of applications that plug into the Office platform

If you would like some assistance with the deployment of Office 2007 at your workplace please feel free to give us a call.