Many DLL error messages on start up

Here's a whole list of possible fixes (not for the faint of heart!):

http://pcsupport.about.com/od/findbyerrormessage/a/dxgi-dll-not-found-missing-error.htm

Visit the given link below:
support.microsoft.com/kb/921914,
You can also avail our technical support by visiting our website: http://www.vtechsquad.com.

You have not said which OS you are using so; from http://support.microsoft.com/kb/943144

When you try to install Windows updates from the Windows Update Web site, the Microsoft Update Web site, or by using Automatic Update, you receive a message that the update is not installed successfully. Additionally, the update is not displayed in the update history.

You may experience this issue in the following scenarios:

Scenario 1 You try to install updates after repair a Windows XP installation by using the Windows XP CD.
Scenario 2 You perform the following operations before you try to install Windows updates:

You perform a new installation of Windows XP Service Pack 2 (SP2).
You visit the Windows Update Web site, or the Microsoft Update Web site.
Note When you visit the update Web site, the latest version of Windows Update software will be installed in your computer.
You install Windows XP Service Pack (SP3) without a restart.
You try to install Windows updates after the install of Windows XP SP3.

Then cause ;

This issue occurs because the Wups2.dll file that is included in the latest version of Windows Update is not installed correctly.

For scenario 1, the registry entries that correspond to the Wups2.dll file are missing after the repair install of Windows XP. The release version of Windows XP does not contain the Windows Update software.

For scenario 2, the registry entries that correspond to Windows Update are changed back to the Windows XP SP2 version if you did not restart the computer before you install Windows XP SP3. The registry entries for the Wups2.dll file are changed to pointing to the Wups.dll file that is included in the release version of Windows XP SP2.
To resolve this problem, use one of the following methods;

Method 1: Download and install the Windows Update Agent,
For an x86-based computer; http://download.windowsupdate.com/WindowsUpdate/redist/standalone/7.4.7600.226/WindowsUpdateAgent30-x86.exe

For an x64-based computer http://download.windowsupdate.com/WindowsUpdate/redist/standalone/7.4.7600.226/WindowsUpdateAgent30-x64.exe

Method 2: Register the Wups2.dll file,

To have MS register the Wups2.dll file in Windows for you, go to http://support.microsoft.com/kb/943144#FixItForMeAlways.

If you prefer to fix this problem yourself,

To register the Wups2.dll file in Windows, follow these steps:

1. Stop the Automatic Updates service. To do this, follow these steps:
a. Open the Command Prompt window. To do this, click Start, click Run, type cmd, and then click OK.
b. At the command prompt, type the following command, and then press ENTER:
net stop wuauserv

2. Register the Wups2.dll file. To do this, follow these steps:

a. At the command prompt, type the following command, and then press ENTER:
regsvr32 %windir%\system32\wups2.dll

Note For a computer that is running Windows XP Professional x64 Edition, type the following command, and then press ENTER:
regsvr32 %windir%\syswow64\wups2.dll

b. Click OK if you receive a verification message.

3. Start the Automatic Updates service. To do this, type the following command at the command prompt, and then press ENTER:
net start wuauserv

4. Exit the Command Prompt window. To do this, type exit at the command prompt, and then press ENTER.

You have to start your PC with the XP cd-rom install disk, if you have
one.

Then, when you come to the screen with the following option displayed :


To repair a Windows XP installation using
Recovery Console, press R.


Then press [R] to start 'Recovery Console'

When confronted by a prompt asking you for Administrator password - just
press [ENTER]

Once in RC has started - type the following command :


expand x:\i386\hal.dl_ c:\windows\system32\hal.dll


(where [x:] is your cd drive-letter)

*NB If SP3 is installed - then the command you type must be :


copy c:\windows\ServicePackFiles\i386\hal.dll c:\windows\system32


....instead, as the files are of two different revision levels
(versions).


Then reboot.

To all that run into this problem like I have, here is the solution:

To install Suretrak 3.0 if you get “unable to find serial#” error:

1. Temporarily Stop the Pervasive Sql Server Workgroup engine
2. Install Suretrak
3. After installation, copy wbtrcall.dll and wbtrv32.dll from the c:\pvsw\bin folder and paste to c:\windows\system and c:\windows\system32

Restart computer; all should be working now

Adrian ([email protected])

did you update from sp2 to sp3 remove sp3 for one reason
fixed it by going to Windows Defender, Tools - Software Explorer and
disabled AirGCFG.exe from automatically starting at boot.** Now I don't get the error message and
the Dlink NIC card works just fine.
AirGCFG is a NIC monitoring function and the NIC will work without it.
Dlink was advised and reported back that SP3 was still Beta and they may work on the problem after
MS releases the final SP3.
I informed them that they did not know what was what and I would not hold my breath until they fix
the problem.
Found out the problem was due to a new version of the wlanapi.dll file introduced with SP3 that
conflicts with the Dlink monitoring file.

** Note: AirGCFG did not show up in the "msconfig" startup listing. But does show in Windows
Defender, with an explanation of what it does.

Hello EricS777

The part where it looks like your xp stuff and vista stuff switch drives is normal. Only the Operating System associates the hard drives by letters this does not mean your hard drive files are switching. This happens because D: drive is Root of Vista OS and Root of any OS in windows gets the C: drive lettering.

dwwin.exe, drwtsn.exe dll is the "Microsoft Application Error Reporting" tool.

I think the message means that something is crashing during system shutdown. When the crash occurs the OS launches dwwin.exe to report the error, however the windows operating system is shutting down and so the application can't launch make the system lockup or hang.

Your problem isn't with dwwin.exe, you need to find out what is actually crashing at shutdown.

If you can`t find out what it is, try going to Administrative Tools/Services and disable the “Error Reporting Service”. You don`t want that running anyway.

Also right click My Computer/Properties/Advanced/Error Reporting
Put a check at both
Disable Error Reporting
But notify me when critical errors occur

Then, if that was the cause and the message stops, we`ll have to try to identify the cause.

what is the error message that you're getting.. usually windows vista will not downgrade your operating system to windows xp. You may need to remove vista before you can load xp.
make sure to save a back up of all of your important files before you do that.

It means : SP3 introduced a new wireless lan application programming interface (windows program that interacts with your wireless card/device driver)

solution : check your wireless device or computer manufacturer for updated (works with SP3) driver.

no vga input message means that the monitor is working fine, and the problem is probably your pc. check the cable connecting the monitor to the pc. if that is ok, you ma have to open up the pc and check some components, most likely the RAM