This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 17%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I've downloaded the SQL Driver and OLE DB driver 9th April 2024 and have attempt to install by running as admin and powershell command.
Powershell command "Start-Process -FilePath "C:\Temp\security-package.exe" -Wait"
I have restarted the server post the activity, but I don't see the update under "View installed updates"
Information based on event logs "Windows Installer installed the product. Product Name: Microsoft ODBC Driver 17 for SQL Server. Product Version: 17.10.6.1. Product Language: 1028. Manufacturer: Microsoft Corporation. Installation success or error status: 1603"
Please share your inputs and questions, thanks!
When you manually install software, why should it be shown under Windows LiveUpdate history?
What are you referring to by Windows LiveUpdate history? Can you share regarding that. Typically after I install a security patch for a non-internet server. The patch will be shown in control panel > Program and features > View installed updates.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 17%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EZH%3C/text%3E%3C/svg%3E)
Hi Azim,
Thank you for posting in Q&A forum.
Error status 1603 usually means that a serious error occurred during the installation process, resulting in installation failure. This error code is relatively common and may be caused by a variety of reasons, including but not limited to permission issues, damaged installation packages, antivirus software interference, etc. It is recommended that you try the following steps to troubleshoot:
1.The original installation package may be damaged. Try to re-download the installation file from the official channel.
2.Temporarily disable antivirus software and firewalls to prevent them from accidentally intercepting necessary operations during the installation process.
3.Make sure the Windows Installer service is running. Press Win+R, enter services.msc, then find the "Windows Installer" service and make sure its status is "Running".
You can also refer to the following links:
I hope the information above is helpful.
Best regards
Zunhui
============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.
Hi @Zunhui Han ,
Thank you for sharing your input.
I've followed the suggested steps and reviewed the article. While I don't see the security patch/update that I ran listed under installed apps and features, I do see the updated SQL driver and OLE DB driver which I installed.
The article mentioned the MSI package but not the security patch. For my current scenario, which involves installing the security patch/update, does installing the latest driver suffice to patch the vulnerabilities?"
Thank you for your reply. It is recommended that you completely uninstall the driver and then try to reinstall the driver. Updating the system to the latest version may solve the compatibility issues of some applications.
Hi @Zunhui Han
Sure! Does reinstalling the Microsoft ODBC Driver 17 and SQL OLE DB Drivers suffice to patch the vulnerabilities or do I have reinstalled the driver and attempt to install the security patches as well?