Error: The Service Pack cannot be integrated into a destination that also has integrated Software Updates

System Requirements:

  • Windows 2000
  • Windows XP
  • Windows Server 2003

The Problem:

When you attempt to slipstream a service pack into your Windows installation media you receive the following error message:

The Service Pack cannot be integrated into a destination that also has integrated Software Updates.
Consult the Service Pack documentation for more details about supported integration scenarios.

Integration Error

The slipstream integration process subsequently terminates without making changes to your deployment share.


More Information:

The redistributable media that you are using has been slipstreamed using QFE updates (not just Service Pack updates but regular patches as well). The Windows Service Pack integrator is unable to adapt to having updates in the install process which would clearly conflict with the new Service Pack version itself (for example you could not apply a RTM or SP1 update to an SP2 install).

To fix the problem, ideally you should attempt to locate a clean installation medium, however if all you have is the QFE integrated disc – such as the ones that Dell ship with many of their own systems.- the following steps will get you around the error.

  1. Open your Deployment share
  2. Open the i386 folder
  3. Delete the directory called:
  4. Locate and open the .inf file called:
  5. For every .exe referenced in the [SetupHotfixesToRun] section, perform a file search of the i386 directory for the file name (minus the .exe) e.g. Q306676.EXE search for Q306676
  6. Delete any files that come back as a result of the search
  7. Close SVCPACK.INF
  8. Delete SVCPACK.INF

You will now be able to slipstream integrate the Service Pack update.

Deploying Internet Explorer 7.0 from a Slipstreamed Windows XP CD

System Requirements:

  • Windows XP Home Edition
  • Windows XP Professional Edition

The Problem:

This article follows on from my integrating Windows XP SP3 with Windows Media Player 11 guide. The aim of the article is to discuss the simplest way to deploy Internet Explorer 7.0 from the CD, automatically and without using third-party software.


More Information:

Yes, there are automated, third party integration methods for this, but you wouldn’t use them in a commercial environment (sensibly).

If you want IE7 to install, and are not fussed about it being ‘integrated’ then the following will get you to where you want to go under both XP Home and Professional Edition. It should also work with the soon to be released Internet Explorer 8 come its RTM towards the end of the year.

Please note that the following is CASE SENSITIVE and should be followed to the LETTER:

  1. Open c:\integrated (from the XP SP3 + WMP11 Slipstream Guide) or substitute with your own folder with the CD files inside where applicable
  2. Create a new folder called:
  3. Create a new .txt file in c:\integrated\$OEM$\ called:
  4. Open CMDLINES.TXT in notepad and add:
“rundll32 setupapi,InstallHinfSection DefaultInstall 128 .\OPTIONS.INF”
“cmd /c start /min cmd /c .\AddOEM.bat”
  1. Create a new .bat file in c:\integrated\$OEM$\ called:
  2. Open AddOEM.bat in notepad and add:
mkdir %SystemDrive%\$Setup
copy .\IE7INST.exe %SystemDrive%\$Setup
  1. Download IE7-WindowsXP-x86-enu.exe (the IE7 installer) into c:\integrated\$OEM$\
  2. Rename IE7-WindowsXP-x86-enu.exe to IE7INST.exe
  3. Create a new .inf file in c:\integrated\$OEM$\ called:
  4. Open OPTIONS.INF in notepad and add:

HKLM,”Software\Microsoft\Windows\CurrentVersion\RunOnceEx\1001″,”IE7 Update”,,”%30%\$Setup\IE7INST.exe /passive /nobackup /update-no /forcerestart”

  1. Open c:\integrated\i386
  2. If it does not already exist, create a new .txt file called:
  3. Open unattend.txt in notepad and enter the following, integrating or overwriting (recommended for novices) the entire file content with:




  1. Burn the revised c:\integration folder to disc as normal to create a bootable slipstream CD

If you have followed these steps correctly then you will be able to install the integrated XP SP3 + Windows Media Player 11 package that I demonstrate how to build here and have IE7 installed by the time you first get to the desktop.
There will be an extra reboot involved as the updated Internet Explorer is applied during the initial post-install startup.

Should you wish to patch Internet Explorer 7.0 as part of this process, you will need to modify the AddOEM.bat, OPTIONS.inf and contents of the $OEM$ folder with the patch files, file copy commands and installation processes. Do remember to ensure that the RunOnceEx run number is > 1001 so that the patch is applied after the installation of IE7.

You will not be able to uninstall Internet Explorer 7 from the machine using these scripts. If you require uninstallation support for IE7 then remove “/nobackup” from the OPTIONS.INF file IE7Updt.AddReg line.

Known Issues

  1. This method causes a reboot before the completion of the first boot to a user desktop. There is a quirk involved in this which means that the account that you configure during setup (administrator under XP Professional) will ultimately load with luna, the Windows XP visual style disabled. You can re-enable this from Desktop in the Control Panel should you want to use Windows Luna.
  2. The folder $Setup will remain on the root of C:\ after the installation has completed. You can safely delete this folder.

ADODB.Connection error ‘800a0e7a’ – Provider cannot be found. It may not be properly installed

System Requirements:

  • Windows NT 4.0
  • Windows 2000
  • Windows XP (x86)
  • Windows Server 2003 (x86)
  • Windows Server 2008 (x86)
  • Windows 7 (x86)
  • Windows Server 2003 (x64)
  • Windows Vista (x64)
  • Windows 7 (x64)
  • Windows Server 2008 (x64)
  • Windows Server 2008 R2 (x64)
  • Windows Server 2012 (x64)

The Problem:

When you attempt to connect to a Microsoft Access database using the ODBC provider Microsoft.Jet.OLEDB.4.0 you receive the error message:

ADODB.Connection error ‘800a0e7a’
Provider cannot be found. It may not be properly installed./path/file.asp, line ##


More Information:

For x64 Systems:

The Microsoft.Jet.OLEDB.4.0 is only available as a 32-bit (x86) module. In order to use it via IIS you must change the web site to run in a 32-bit application pool.

Under IIS 7.0, 7.5 or 8.0:

  • Assuming that you will not want to use ASP .net, in the IIS console in the Application Pools section, create a no managed code, integrated application pool. If you do want to maintain access to ASP .net, select the framework version you require.
  • Once created, in its advanced settings set “Enable 32-bit Applications” to true
  • In the Basic Settings… for the web site entry you are experiencing the error on, change the Application Pool to the newly created 32-bit pool.
  • Restart the web site

In most cases where the system is running under an x64 architecture, this should fix the problem.

For x86 and x64 Systems:

We had a server down for an entire day because of this one. It was either an attempt to fix a security database fault, or an update from Microsoft Update delivered in the April 2008 patch cycle, but after the reboot for the patches, none of the JET (Access) databases on the particular server, in any IIS web would operate.

I will simply cut to the fix for you in the beginning, to expedite your likely finding of a resolution to this problem. Something had caused the service provider for the Microsoft.Jet.OLEDB.4.0 provider to become unregistered. To fix the problem issue the following command from a Command Prompt or Run:

regsvr32.exe msjetoledb40.dll

You shouldn’t need to reboot to solve the problem, it didn’t in my case. However, if nothing happens do restart before progressing to the next step.


Additional Steps: Step 1

Reregister the components from MDAC, JET and ADO in their entirety. Simply copy the below into a BAT file and run it.

:: ADODB.Connection error '800a0e7a'

:: Provider cannot be found. It may not be properly installed.regsvr32.exe cfgmgr32.dll -s

regsvr32.exe cliconfg.dll -s

regsvr32.exe dasetupr.dll -s

regsvr32.exe dbmsgnet.dll -s

regsvr32.exe dbmsrpcn.dll -s

regsvr32.exe dbnetlib.dll -s

regsvr32.exe dbnmpntw.dll -s

regsvr32.exe expsrv.dll -s

regsvr32.exe msadce.dll -s

regsvr32.exe msadcer.dll -s

regsvr32.exe msadcf.dll -s

regsvr32.exe msadcfr.dll -s

regsvr32.exe msadco.dll -s

regsvr32.exe msadcor.dll -s

regsvr32.exe msadcs.dll -s

regsvr32.exe msadds.dll -s

regsvr32.exe msaddsr.dll -s

regsvr32.exe msader15.dll -s

regsvr32.exe msado15.dll -s

regsvr32.exe msadomd.dll -s

regsvr32.exe msador15.dll -s

regsvr32.exe msADOX.dll -s

regsvr32.exe msadrh15.dll -s

regsvr32.exe mscpxl32.dll -s

regsvr32.exe msdadc.dll -s

regsvr32.exe msdadiag.dll -s

regsvr32.exe msdaenum.dll -s

regsvr32.exe msdaer.dll -s

regsvr32.exe msdaora.dll -s

regsvr32.exe msdaorar.dll -s

regsvr32.exe MSDAOSP.dll -s

regsvr32.exe msdaprsr.dll -s

regsvr32.exe msdaprst.dll -s

regsvr32.exe msdaps.dll -s

regsvr32.exe msdarem.dll -s

regsvr32.exe msdaremr.dll -s

regsvr32.exe msdart.dll -s

regsvr32.exe msdasc.dll -s

regsvr32.exe msdasql.dll -s

regsvr32.exe msdasqlr.dll -s

regsvr32.exe msdatl3.dll -s

regsvr32.exe msdatt.dll -s

regsvr32.exe msdaurl.dll -s

regsvr32.exe msdfmap.dll -s

regsvr32.exe msjro.dll -s

regsvr32.exe msjtes40.dll -s

regsvr32.exe msorc32r.dll -s

regsvr32.exe msorcl32.dll -s

regsvr32.exe msvcirt.dll -s

regsvr32.exe msvcrt.dll -s

regsvr32.exe mswdat10.dll -s

regsvr32.exe mswstr10.dll -s

regsvr32.exe msxactps.dll -s

regsvr32.exe msxml3.dll -s

regsvr32.exe msxml3a.dll -s

regsvr32.exe msxml3r.dll -s

regsvr32.exe mtxdm.dll -s

regsvr32.exe mtxoci.dll -s

regsvr32.exe odbc16gt.dll -s

regsvr32.exe ODBC32.dll -s

regsvr32.exe ODBC32GT.dll -s

regsvr32.exe odbcbcp.dll -s

regsvr32.exe odbcconf.dll -s

regsvr32.exe ODBCCP32.dll -s

regsvr32.exe ODBCCR32.dll -s

regsvr32.exe ODBCCU32.dll -s

regsvr32.exe ODBCINT.dll -s

regsvr32.exe ODBCTRAC.dll -s

regsvr32.exe oledb32.dll -s

regsvr32.exe oledb32a.dll -s

regsvr32.exe oledb32r.dll -s

regsvr32.exe setupapi.dll -s

regsvr32.exe sqloledb.dll -s

regsvr32.exe sqlsrv32.dll -s

regsvr32.exe sqlunirl.dll -s

regsvr32.exe sqlxmlx.dll -s

regsvr32.exe vbajet32.dll -s:: OLEdB

regsvr32.exe %SystemRoot%\System32\msjetoledb40.dll:: Jet

regsvr32.exe %SystemDrive%\Program Files\Common Files\Microsoft Shared\DAOdao360.dll -s

regsvr32.exe %SystemRoot%\System32\expsrv.dll -s

regsvr32.exe %SystemRoot%\System32\msexch40.dll -s

regsvr32.exe %SystemRoot%\System32\msexcl40.dll -s

regsvr32.exe %SystemRoot%\System32\jet500.dll -s

regsvr32.exe %SystemRoot%\System32\msjet35.dll -s

regsvr32.exe %SystemRoot%\System32\msjet40.dll -s

regsvr32.exe %SystemRoot%\System32\msjetol1.dll -s

regsvr32.exe %SystemRoot%\System32\msjint40.dll -s

regsvr32.exe %SystemRoot%\System32\msjter40.dll -s

regsvr32.exe %SystemRoot%\System32\msjtes40.dll -s

regsvr32.exe %SystemRoot%\System32\msltus40.dll -s

regsvr32.exe %SystemRoot%\System32\mspbde40.dll -s

regsvr32.exe %SystemRoot%\System32\msrd2x40.dll -s

regsvr32.exe %SystemRoot%\System32\msrd3x40.dll -s

regsvr32.exe %SystemRoot%\System32\msrepl40.dll -s

regsvr32.exe %SystemRoot%\System32\mstext40.dll -s

regsvr32.exe %SystemRoot%\System32\mswdat10.dll -s

regsvr32.exe %SystemRoot%\System32\mswstr10.dll -s

regsvr32.exe %SystemRoot%\System32\msxbde40.dll -s

regsvr32.exe %SystemRoot%\System32\spmsg.dll -s

regsvr32.exe %SystemRoot%\System32\vbajet32.dll -s

:: ADO
regsvr32.exe %SystemDrive%\Program Files\Common Files\System\ado\msader15.dll -s
regsvr32.exe %SystemDrive%\Program Files\Common Files\System\ado\msado15.dll -s
regsvr32.exe %SystemDrive%\Program Files\Common Files\System\ado\msadomd.dll -s
regsvr32.exe %SystemDrive%\Program Files\Common Files\System\ado\msador15.dll -s
regsvr32.exe %SystemDrive%\Program Files\Common Files\System\ado\msadox.dll -s
regsvr32.exe %SystemDrive%\Program Files\Common Files\System\ado\msadrh15.dll -s
regsvr32.exe %SystemDrive%\Program Files\Common Files\System\ado\msjro.dll -s

Additional Steps: Step 2

Reinstall MDAC 2.8 SP1 (Windows XP SP1 or below only). You will need to perform some registry modifications before you can reinstall MDAC as it is a protected system module.

  1. Open Regedit
  2. Navigate to:
  3. Look through each class ID for the following friendly name values. Delete the Class ID containing the matching friendly names:
    Microsoft MDAC Response Files
    Microsoft MDAC Setup Files
    Microsoft SQL Server ODBC Drivers
    Microsoft SQL Server Net Libs
    Microsoft SQL Server OLEDB Provider
    WebData Setup Exception Package
    Mdac 2.8 Exception Package
  4. Download and reinstall MDAC 2.8 SP1 from Microsoft which should reinstall in full.

Cannot unhide systems files under Windows 2000, XP, 2003 or Vista

System Requirements:

  • Windows 2000, XP, 2003, Vista

The Problem:

When attempting to show hidden files in the Windows Folder Options settings window, the bivariate “So not show hidden files and folders” / “Show hidden files and folders” radio buttons do not have a pre-selected value.

Optionless Radio Buttons

No matter which of the options you chose your system will not display hidden files through Windows Explorer, and will not save the “Show hidden files and folders” setting.

More Info:

This is invariably caused by a virus infection or spyware such as (but by no means exclusive to) W32/DKR.worm.

You need to ensure that you have fully disinfected your system using AntiVirus and AntiSpyware software before making the changes to restore the functionality of the Folder Options applet. Otherwise you are frankly wasting your time by troubleshooting the problem.


Step 1: Why does it do it?

The virus will have modified the default property value of the registry flag responsible for specifying your preference. While Windows Explorer expects to be able to set a DWORD type for the value, the Virus will have changed the registry type to a Reg_SZ, meaning that the system is unable to read to or write to the value – hence you are unable to save your preference change after you have removed the virus from your system.

Note: If you have not removed the virus from your system then there is good reason to believe that the virus itself is preventing you from making any such that so as to prevent its own demise.

Open regedit and navigate to:


Incorrect (Left) : Correct (Right)

Delete the REG_SZ named Hidden, you do not need to manually recreate the DWORD. Don’t celebrate yet, follow step 2 BEFORE you succumb to the spleen bursting need that you now have to view your hidden files. Otherwise you will be doing step 1 again.


Step 2: Repairing the Explorer Default Flag Associations

The virus really did not want you to view hidden files on the PC, so in addition to preventing you from changing the setting, it also ensured that should you attempt to fix the problem, Explorer would simply break the setting itself – thus ensuring that there is no way that Windows Explorer is going to show you hidden files.

Navigate to:


Fix Explorer

Note the presence of the REG_SZ Checked value, this should be a DWORD value. Its job is to tell the Explorer form what to do when someone selects the Show hidden files and folders option, and currently it is being told to write a string value, not a DWORD.

Delete the CheckedValue REG_SZ, create a similarly named DWORD and set its value to equal 1 as shown in the image below.

Fixed Values

You can now view your hidden files and folders.