Возникла ошибка при запуске wsclient dll не найден указанный модуль

На прошлой неделе Microsoft выпустила Windows 10 Preview build 11099 для инсайдеров на Fast Ring, и компания немедленно предупредила нас о сопутствующих проблемах . И некоторые пользователи обнаружили другую проблему во второй сборке Redstone для Windows 10 Preview, но на этот раз у нас есть правильное решение.

Как сообщается, несколько пользователей сказали, что они сталкиваются со странной ошибкой при загрузке своих компьютеров. А именно, сообщение об ошибке «ошибка в wsclient.dll отсутствует запись: RefreshBannedAppsList» появляется при каждом запуске.

Сообщение не влияет на систему, так как оно исчезает, когда вы закрываете его, но, поскольку оно появляется при каждой загрузке, оно действительно раздражает.

Исправить ошибку WSClient.DLL в Windows 10 build 11099

Иногда могут возникать ошибки WSClient.DLL, и, говоря об этих ошибках, пользователи сообщают о некоторых типичных проблемах:

• Ошибка WSClient.dll Windows 8.1 — эта проблема может возникать и в Windows 8.1. Поскольку Windows 8.1 и 10 очень похожи, вы также сможете применить все наши решения к Windows 8.1.
• Произошла ошибка WSClient.dll — это всего лишь вариант исходной ошибки, и в большинстве случаев вы можете решить проблему, выполнив команду WSReset.
• WSClient.dll refreshbannedappslist — иногда определенные задачи в планировщике задач могут вызвать появление этой проблемы, но вы можете исправить ее, найдя и удалив проблемную задачу.
• Rundll32.exe WSClient.dll wsptlr licensing — при появлении этого сообщения об ошибке вы можете исправить проблему, просто перерегистрировав проблемный файл.
• WSClient.dll не найден — в некоторых случаях этот файл может даже не присутствовать на вашем компьютере. Чтобы это исправить, выполните сканирование SFC и DISM. В случае, если это не сработает, вам, возможно, придется переустановить систему.

Решение 1. Выполните команду WSReset.

Если у вас есть проблемы с WSClient.DLL, вы можете решить их, просто запустив команду WSReset. Это довольно просто сделать, и вы можете сделать это, выполнив следующие действия:

1. Откройте меню Win + X. Вы можете сделать это, щелкнув правой кнопкой мыши кнопку « Пуск» или с помощью сочетания клавиш Windows + X.
2. Выберите в меню командную строку (Admin) или PowerShell (Admin) .
   
3. Введите wsreset и нажмите Enter .
   

Через пару секунд процесс будет завершен и проблема должна быть решена.

• ЧИТАЙТЕ ТАКЖЕ: Как исправить поврежденный файл bootres.dll в Windows 10

Решение 2. Отключите задачу WSRefreshBannedAppsListTask

По словам пользователей, иногда определенные задачи в планировщике задач могут вызвать проблемы с WSClient.DLL. Однако вы можете решить эту проблему, просто отключив эти задачи. Для этого выполните следующие действия:

1. Нажмите Windows Key + S и введите планировщик . Выберите Task Scheduler из списка результатов.
   
2. Под планировщиком задач перейдите в Microsoft> Windows> WS .
   
3. Щелкните правой кнопкой мыши задачу WSRefreshBannedAppsListTask и выберите « Отключить» .

После отключения этой задачи проверьте, сохраняется ли проблема. Если эта задача недоступна в планировщике задач, вам следует пропустить это решение и перейти к следующему.

Также стоит упомянуть, что вы можете удалить эту задачу с помощью командной строки. Если вы не хотите иметь дело с планировщиком задач и искать конкретную задачу вручную, вы можете просто удалить ее, выполнив одну команду. Для этого выполните следующие действия:

1. Запустите командную строку от имени администратора. Мы показали вам, как это сделать в предыдущем решении.
2. При запуске командной строки выполните команду schtasks / delete / TN « Microsoft Windows WS WSRefreshBannedAppsListTask» / F.
   

Оба метода похожи, но если вы опытный пользователь или хотите сделать это быстро, вы можете использовать метод командной строки.

Решение 3 — заново зарегистрировать проблемный файл DLL

Иногда вы можете решить проблему с WSClient.DLL, просто перерегистрировав проблемный файл DLL. Этот процесс относительно прост, и вы можете сделать это, выполнив следующие действия:

1. Запустите командную строку от имени администратора.
2. При запуске командной строки выполните следующие команды:

• regsvr32 / u WSClient.dll
• regsvr32 / i WSClient.dll

После выполнения обеих этих команд вы повторно зарегистрируете проблемный файл DLL, и проблема должна быть решена.

• ЧИТАЙТЕ ТАКЖЕ: ИСПРАВЛЕНИЕ: ошибка VLC «отсутствует libvlc.dll» в Windows 10

Решение 4. Выполните команды SFC и DISM

В некоторых случаях проблемы с WSClient.DLL могут возникнуть из-за повреждения вашей установки Windows. Однако вы можете восстановить его, выполнив сканирование SFC . Это относительно просто, но вы можете сделать это, выполнив следующие действия:

1. Запустите командную строку от имени администратора.
2. Теперь запустите команду sfc / scannow .
   
3. Начнется сканирование SFC. Имейте в виду, что это сканирование может занять около 15 минут, поэтому не мешайте ему.

После того, как сканирование закончено, проверьте, если проблема все еще там. Если проблема сохраняется, или если вы не смогли запустить сканирование SFC, вам придется использовать сканирование DISM . Для этого просто выполните следующие действия:

1. Откройте командную строку как администратор.
2. Введите DISM / Online / Cleanup-Image / RestoreHealth и нажмите Enter, чтобы запустить его.
   
3. Сканирование DISM начнется. Сканирование может занять до 20 минут, поэтому не мешайте ему.

После того, как сканирование полностью завершено, проверьте, сохраняется ли проблема. Если вы раньше не могли запускать сканирование SFC, возможно, вам следует попробовать запустить его снова и проверить, решает ли это проблему.

• Читайте также: Исправлено: сбой DISM в Windows 10

Решение 5 — Изменить ваши DNS-серверы

Ваши DNS-серверы играют большую роль, и иногда проблемы с вашим DNS- сервером могут вызвать ошибку WSClient.DLL. Несколько пользователей сообщили, что им удалось решить эту проблему, просто изменив свои DNS-серверы. Это простая задача, и вы можете сделать это, выполнив следующие действия:

1. Нажмите значок сети на панели задач и выберите сетевое подключение в меню.
   
2. Теперь выберите Изменить параметры адаптера .
   
3. Появится список доступных сетевых подключений. Щелкните правой кнопкой мыши ваше сетевое подключение и выберите Свойства .
   
4. Выберите Протокол Интернета версии 4 (TCP / IPv4) и нажмите кнопку Свойства .
   
5. Выберите параметр Использовать следующие адреса DNS-серверов . Введите 8.8.8.8 в качестве предпочтительного и 8.8.4.4 в качестве альтернативного DNS-сервера . Нажмите OK, чтобы сохранить изменения.
   

После внесения этих изменений вы перейдете на DNS от Google, и проблема должна быть решена. Если вы хотите, вы можете использовать другой DNS-сервер, такой как OpenDNS.

• ЧИТАЙТЕ ТАКЖЕ: Исправьте сообщения об ошибках Ntdll.dll в Windows 10, 8.1

Решение 6 — Выполнить восстановление системы

Если проблема с WSClient.DLL начала появляться недавно, вы можете решить ее, просто выполнив Восстановление системы . В случае, если вы не знаете, восстановление системы — это встроенная функция, которая позволяет восстановить вашу систему до прежнего состояния и устранить все виды проблем.

Чтобы выполнить восстановление системы, вам просто нужно сделать следующее:

1. Нажмите Windows Key + S и введите восстановление системы . Теперь выберите Создать точку восстановления .
   
2. Когда появится окно « Свойства системы» , нажмите кнопку « Восстановление системы» .
   
3. Откроется окно восстановления системы . Нажмите Далее, чтобы продолжить.
   
4. Если доступно, установите флажок Показать больше точек восстановления . Выберите нужную точку восстановления и нажмите « Далее» .
   
5. Следуйте инструкциям на экране для завершения процесса восстановления.

После того, как ваш компьютер вернется в исходное состояние, проверьте, сохраняется ли проблема.

• Читайте также: Исправлено: Windows 10 работает медленно после восстановления системы

Решение 7. Выполните обновление на месте

В некоторых случаях единственный способ исправить ошибку WSClient.DLL — выполнить обновление на месте. Если вы не знаете, обновление на месте переустановит Windows и обновит ее до последней версии.

Мы также должны упомянуть, что этот процесс сохранит все ваши файлы и приложения, что также является большим плюсом.

Чтобы выполнить обновление на месте, выполните следующие действия.

1. Скачайте и запустите Media Creation Tool .
2. Выберите Обновить этот компьютер сейчас .
3. Выберите « Загрузить и установить обновления» (рекомендуется) и нажмите « Далее» . Этот шаг не является обязательным, поэтому вы можете пропустить его, если хотите.
4. Следуйте инструкциям на экране, пока не дойдете до экрана Готов к установке . Выберите Изменить, что оставить .
5. Выберите Сохранить личные файлы и приложения и нажмите Далее .
6. Следуйте инструкциям, чтобы завершить процесс.

После завершения процесса у вас будет новая установка Windows 10, и все ваши файлы и приложения будут сохранены, и проблема должна быть решена.

Связанный: Как исправить поврежденные изображения онлайн [Лучшие инструменты для использования в 2018]

Выполнение одного из этих решений должно решить проблему с сообщением об ошибке WSClient.DLL. Если вы заметили какую-то другую ошибку в сборке 11099, сообщите нам об этом в комментариях.

Примечание редактора : этот пост был первоначально опубликован в январе 2016 года и с тех пор был полностью переработан и обновлен для обеспечения свежести, точности и полноты

ЧИТАЙТЕ ТАКЖЕ:

• Исправлено: XAudio2_6.dll отсутствует в Windows 10
• Как исправить ошибки mfc100.dll в Windows 10, 8.1
• ИСПРАВЛЕНИЕ: «Gdi32full.dll отсутствует» (или не был найден) ошибка в Windows 10

Some Windows 10 users have been troubled by another annoying DLL error, and they wish to get rid of it immediately. Thankfully, we’ve got the solutions for it in this article.

Reportedly, a few users said that they encounter a strange bug when they boot up their computers. Some others said they get the error message saying wsclient.dll is not a valid win32.

Others got the error message saying error in wsclient.dll Missing entry: RefreshBannedAppsList appears on every startup. However, what is this wsclient.dll problem?

The message doesn’t affect the system, as it disappears when you close it, but since it shows up on every boot, it’s really annoying.

WSClient.DLL errors can sometimes occur, and speaking of these errors, here are some common issues that users reported:

• WSClient.dll error Windows 8.1 – wsclient.dll error can appear on Windows 8.1 as well. Since Windows 8.1 and 10 are so similar, you should be able to apply all of our solutions to Windows 8.1 as well.
• WSClient.dll error has occurred – This is just a variation of the original error, and in most cases, you can fix the issue by running the WSReset command.
• WSClient.dll refreshbannedappslist – Sometimes certain tasks in Task Scheduler can cause this issue to appear, but you can fix it by finding and removing the problematic task.
• Rundll32.exe WSClient.dll wsptlr licensing – If this error message occurs, you might be able to fix the issue simply by re-registering the problematic file.
• WSClient.dll not found – In some cases, this file might not be even present on your PC. To fix that, perform SFC and DISM scans. In case that doesn’t work, you might have to reinstall your system.

How do I fix WSClient.DLL error in Windows 10?

1. Use a specialized tool

A go-to solution for fixing WSClient.DLL errors is by using repair software because it can proceed with this task automatically.

In addition, it can scan other stability issues on your PC and replace them with healthy parts, thus increasing its overall performance.

2. Perform a WSReset command

1. Open Win + X menu. You can do that by right-clicking the Start Button or by using Windows Key + X shortcut.
2. Choose Command Prompt (Admin) or PowerShell (Admin) from the menu.
   
3. Enter wsreset and press Enter.
   

After a couple of moments, the process will be finished and the issue should be resolved.

If you’re having issues with the WSClient.DLL error starting Windows, you might solve them simply by running a WSReset command. This is quite straightforward to do, and you can do it by following the steps above.

3. Disable the WSRefreshBannedAppsListTask

1. Press Windows Key + S and enter scheduler. Select Task Scheduler from the list of results.
   
2. Under Task Scheduler, go to Microsoft>Windows>WS.
   
3. Right click on the task WSRefreshBannedAppsListTask, and choose Disable.

After disabling this task, check if the problem is still there. In case this task isn’t available in Task Scheduler, you should skip this solution and move to next one.

According to users, sometimes certain tasks in Task Scheduler can cause problems with WSClient.DLL. However, you can fix this issue simply by disabling these tasks.

It’s also worth mentioning that you can remove this task using the Command Prompt. You can just remove it by running a single command. To do that, follow these steps:

1. Start Command Prompt as administrator. We showed you how to do that in the previous solution.
2. When Command Prompt starts, run the following command: schtasks /delete /TN "MicrosoftWindowsWSWSRefreshBannedAppsListTask" /F
   

Both methods are similar, but if you’re an advanced user or if you want to do it quickly, you might use the command line method.

4. Re-register the problematic DLL file

1. Start Command Prompt as an administrator.
2. When Command Prompt starts, run the following command: regsvr32 /u WSClient.dll

3. Then, run another command: regsvr32 /i WSClient.dll

4. Close the Command Prompt, and you should be set.

After running both of these commands, you’ll re-register the problematic DLL file and the issue should be resolved.

Sometimes you might be able to fix the problem with WSClient.DLL simply by re-registering the problematic DLL file. This process is relatively simple and you can do it by following the steps above.

4. Run SFC and DISM commands

1. Start Command Prompt as an administrator.
2. Now run the following command: sfc /scannow
   
3. The SFC scan will start. Keep in mind that this scan can take about 15 minutes, so don’t interfere with it.

Once the scan is finished check if the problem is still there. In case the issue is still present, or if you weren’t able to run the SFC scan, you’ll have to use DISM scan instead. To do that, just follow these steps:

1. Open Command Prompt as an administrator.
2. Type the following command: DISM /Online /Cleanup-Image /RestoreHealth
   
3. DISM scan will now start. The scan can take up to 20 minutes, so don’t interfere with it.

Once the scan is completely finished, check if the problem is still there. If you weren’t able to run an SFC scan before, perhaps you should try to run it again and check if that solves the issue.

In some cases, problems with WSClient.DLL can occur because your Windows installation is damaged. However, you might be able to repair it by performing an SFC scan.

5. Change your DNS servers

1. Click the network icon on your Taskbar and choose your network connection from the menu.
   
2. Now select Change adapter options.
   
3. A list of available network connections will appear. Right-click your network connection and choose Properties.
   
4. Select Internet Protocol Version 4 (TCP/IPv4) and click the Properties button.
   
5. Select Use the following DNS server addresses option.
6. Enter 8.8.8.8 as the Preferred.
7. Now enter 8.8.4.4 as the Alternate DNS server. Click OK to save changes.
   
   

After making these changes, you’ll switch to Google’s DNS and the problem should be resolved. If you want, you can use a different DNS server such as OpenDNS.

Your DNS servers play a large role, and sometimes issues with your DNS can cause WSClient.DLL error to appear. Several users reported that they managed to fix this issue simply by changing their DNS servers.

6. Perform a System Restore

1. Press Windows Key + S and enter system restore.
2. Now select Create a restore point.
   
3. When the System Properties window appears, click System Restore button.
   
4. System Restore window will now open. Click Next to proceed.
   
5. If available, check Show more restore points option. Choose the desired restore point and click Next.
   
6. Follow the instructions on the screen to complete the restoration process.

After your PC is restored to its original state, check if the problem is still there.

If the problem with WSClient.DLL started occurring recently, you might be able to solve it simply by performing a System Restore.

In case you don’t know, System Restore is a built-in feature that allows you to restore your system to the previous state and fix all sorts of issues.

7. Perform an in-place upgrade

1. Download and run Media Creation Tool.
2. Select Upgrade this PC now.
   
3. Select Download and install updates (recommended) option and click Next. This step isn’t mandatory, so you can skip it if you want.
4. Follow the instructions on the screen until you reach Ready to install screen. Select Change what to keep.
5. Select Keep personal files and apps and click Next.
   
6. Follow the instructions to complete the process.

Once the process is finished, you’ll have a fresh installation of Windows 10, all your files and applications will be preserved, and the problem should be resolved.

We also have to mention that this process will keep all your files and applications, which is also a big plus.

In some cases, the only way to fix WSClient.DLL error is to perform an in-place upgrade. In case you don’t know, an in-place upgrade will reinstall Windows and update it to the latest version.

Performing one of these solutions should solve the problem with WSClient.DLL error message. If you noticed some other bug in the build 11099, let us know in the comment section below.

Question

Issue: How to fix WSClient.dll error in Windows?

Hello. I keep receiving the “WSClient.dll could not be found” error on my Windows PC. What do I do? Any tips would be appreciated.

Solved Answer

WSClient.dll is a dynamic link library file^[1] that is used by various programs in Windows systems. It contains code and data that are shared by multiple applications, which allows them to run more efficiently and effectively. However, when the WSClient.dll file becomes missing, corrupted, or otherwise damaged, it can cause errors like the ones listed below:

• Failed to load WSClient.dll
• Access Violation at address – WSClient.dll
• The application has failed to start because WSClient.dll was not found
• WSClient.dll library error
• Cannot find C:WindowsSystem32WSClient.dll
• The file WSClient.dll is missing or corrupt
• Cannot start Windows. A required component is missing: WSClient.dll. Please install Windows again.
• This application failed to start because WSClient.dll was not found. Re-installing the application may fix this problem.
• Cannot register WSClient.dll
• WSClient.dll could not be found

These errors can prevent the affected programs from running or cause other issues with the system. DLL files play an important role in Windows systems as they contain code that can be used by multiple programs at the same time, reducing memory usage and making the system more efficient.

In this guide, you will find 8 steps that should help you fix the WSClient.dll error in Windows. Keep in mind that the manual troubleshooting process can be lengthy. You can use a maintenance tool like FortectMac Washing Machine X9 that can fix most system errors, BSODs,^[2] corrupted files, and registry^[3] issues automatically. Otherwise, follow the step-by-step instructions below.

Solution 1. Fix Corrupted System Files

Use Command Prompt commands to repair system file corruption:

• Open Command Prompt as administrator
• Use the following command and press Enter:
  sfc /scannow

• Reboot your system
• If SFC returned an error, then use the following command lines, pressing Enter after each:
  DISM /Online /Cleanup-Image /CheckHealth
  DISM /Online /Cleanup-Image /ScanHealth
  DISM /Online /Cleanup-Image /RestoreHealth

Solution 2. Install Windows Updates

• Click Start and select Settings
• Go to the Windows Update section
• Click Check for updates and wait

• Go to the Advanced options and install optional updates
• Reboot your system

Solution 3. Update Drivers

Outdated drivers could be the cause of this issue. In this case, you can fix it automatically by using DriverFix, which will scan your PC for missing and out-of-date device drivers. Or you can update them manually:

• Open Settings
• Click on Update & Security
• Click on Windows Update
• Click the Check for updates button
• Click the View optional updates option
• Click the Driver updates tab
• Select the driver you want to update
• Click the Download and install button

If the View optional updates link is not available after checking for updates, then Windows Update does not have any new drivers or any updates for other products at that particular time.

Solution 4. Re-register WSClient.dll

• Run Command Prompt as administrator
• Run the following commands one by one and press Enter after each:

regsvr32 /u WSClient.dll

regsvr32 /i WSClient.dll

• WSClient.dll is now re-registered and the problem should be resolved

Solution 5. Change DNS Server

• Press the Windows key + R to open the Run box
• Type ncpa.cpl and hit Enter to open Network Connections
• Right-click on the network adapter that you use most frequently and choose Properties
• In the Networking tab, choose Internet Protocol Version 4 (TCP/IPv4) and hit Properties
• In the General tab, tick Use the following DNS server addresses and set Preferred DNS server to 8.8.8.8 and Alternate DNS server to 8.8.4.4

• Check Validate settings upon exit and hit OK to save the changes

Solution 6. Download WSClient.dll

If you receive an error that says WSClient.dll is missing or not found you can try downloading the file manually.

• Go to the WSClient.dll download page to find the appropriate WSClient.dll version, and download it

Note: Make sure to choose the correct version for your system (32-bit or 64-bit) and the latest version for the best performance.

• After downloading, extract the archive to your desktop and verify the MD5 and SHA-1 of the file to the database
• Place the file within the Windows system directory (C:WindowsSystem32 in Windows 10/8.1/8)
• Reboot your computer and relaunch the problematic programs to see if they work properly.

Solution 7. Use System Restore

System Restore is a feature in Microsoft Windows that allows users to revert their computer’s state to a previous point in time. This can be helpful if you have made changes to your system that are causing problems.

• Go to the Start menu, type restore, and click on Create a restore point
• Click System Restore, then follow the prompts until you can select a restore point
• Select the one you want (ideally before the issue started occurring) and go ahead with the process

Solution 8. Try a Workaround

• Open Command Prompt with administrative rights
• Run the following command:

schtasks /delete /TN “MicrosoftWindowsWSWSRefreshBannedAppsListTask” /F

Repair your Errors automatically

ugetfix.com team is trying to do its best to help users find the best solutions for eliminating their errors. If you don’t want to struggle with manual repair techniques, please use the automatic software. All recommended products have been tested and approved by our professionals. Tools that you can use to fix your error are listed bellow:

The error WSClient.dll (Missing entry: RefreshBannedAppsList) will typically occur when the Windows OS boots up or is restarted. You can click away and close the error with no consequence, but the error will reappear the next time your PC boots up. This problem is confirmed to occur on both Windows 10 and Windows 11. 

If you experience the same problem on Windows 10 or Windows 11, there are a few common causes why you might see this error popup at every system startup: outdated Windows build, system file corruption, corrupted Windows cache, de-registered WSclient.DLL file, active WSRefreshBannedAppsListTask task, 3rd party interference or an inconsistent DNS. 

If you haven’t managed to fix your issue yet, follow the methods below to troubleshoot the issue away regardless of your Windows version.

1. Update Windows to Latest Version

Looking back, the first major surge of WSClient.DLL errors happened when Microsoft rolled out build 11099 for Insider Preview builds of Windows 10. Since then, the issue has not been completely eradicated despite the fact that Microsoft has pushed several different hotfixes aimed at resolving this issue.

However, it’s still worth installing these hotfixes since they might just make the error go away. One of these hotfixes will specifically prevent WSRefreshBannedAppsListTask (the task responsible for throwing this startup error) from spawning startup points that will raise this error.

If you have outstanding updates that you keep delaying and you get this message every time you start or restart your computer, applying all pending Windows updates should in most cases resolve the issue.

Here’s how to carry on this procedure:

Note: the following methods apply to both Windows 10 and Windows 11.

1. Use the keyboard shortcut Windows key + R to launch the Run dialog box.
2. To open the Windows Settings menu, enter “ms-settings:” and hit Enter.

   Note: If User Account Control requests administrative authority, choose “Yes.”

3. Select Windows Update from the menu on the left side of the Settings screen.
4. On the subsequent screen, select Check for Updates to determine whether any updates need to be installed.
5. Click Download & Install if the driver is ready for installation.
6. Be patient and wait for all required updates to be released. It may be necessary to restart your computer for the changes to take effect.
7. Restart your computer and see if the WsClient.DLL error is now fixed. 

2. Run SFC & DISM Scans

The WsClient.DLL startup error could also be related to some kind of system file corruption that affects this dynamic link library (DLL) file.

Luckily, Windows ships with a set of tools (SFC & DISM) that allow you to diagnose typical system file corruption and fix the vast majority of them with no manual user intervention. 

You can run both of these tools in quick succession from an elevated Command Prompt window and essentially fix the underlying causes of this error.

Here’s a quick step-by-step guide that will walk you through the process of running System File Checker and Deployment Image Servicing & Management scans:

1. Press the Windows key + R to launch the Run dialog box.
2. Next, type “cmd” and press Ctrl + Shift + Enter to launch a Command Prompt with elevated privileges.
3. Click Yes on the User Account Control (UAC) prompt to give administrative access.
4. At the elevated CMD line, execute the following command and press Enter to execute the first SFC scan:

   sfc /scannow

   Note: The SFC tool has a proneness to freeze in the middle of a scan, despite the fact that the scan is still in progress. If you see this behavior during the scan, do not terminate it, as doing so might cause logical errors on your OS disk. Instead, wait for some time, and the utility should unfreeze by itself.

5. Following the completion of the SFC scan, let’s do a DISM scan. Enter the following command to accomplish this:

   Dism /Online /Cleanup-Image /CheckHealth

   Note: DSM utilizes a subcomponent of Windows Update to download healthy copies to repair faulty system files; hence, an internet connection is necessary to execute this sort of scan.

6. Once both types of scans have been completed successfully, reboot your PC and see if the problem is now fixed. 

3. Reset the Windows Store cache

If you also get this error pop-up when opening the Windows Store or an associated dependency, the issue is most likely caused by a Windows Sore cache issue.

This is way more common than you think especially on Windows 11 where the cache is prone to break whenever there’s an unexpected interruption when an app is downloaded or updated.

If this scenario looks like it could be applicable, you should be able to fix this issue by resetting the Windows Store using an elevated command prompt. This procedure is quite simple and should be effective in most situations where the Microsoft Store is to blame. 

For step-by-step instructions on resetting the Windows Store cache and addressing the WsClient.DLL startup error:

1. Launch the Command Prompt as the initial step. To accomplish this, press Windows key + R, type ‘cmd’ in the search field, and then press CTRL + Shift + Enter to launch the Command Prompt with administrative rights. 
2. Once the Command Prompt with administrative rights has been launched, you must type the following command and press Enter to continue:

   WSreset.exe

3. After completing these steps, close the elevated Command prompt and see of the startup error is now fixed.

4. Re-register the WSClient.dll

Because WSClient.dll is a Windows Store licensing client file, one of the first things that you should try if you encounter the ‘Missing entry: RefreshBannedAppsList‘ error at every startup is to re-register it.

To do this, you will first need to unregister it from an elevated CMD command, then register it again with a separate command.

Several affected uses that we’re experiencing this pop-in error whenever the WSClient.dll dependency was supposed to be used have managed to fix this by running a series of commands from an elevated CMD to re-register it.

Here’s a quick guide on how to do this:

1. Press Windows key + R to open up a Run dialog box.
2. Next, type ‘cmd’ inside the text box, then press Ctrl + Shift + Enter to open up a Run dialog box. 
3. At the User Account Control (UAC), click Yes to grant admin access. 
4. Once you’re inside the elevated CMD prompt, type the following command to un-register the WSClient.dll:

   regsvr32 /u WSClient.dll

   Note: If the file is already un-registered, this command will not produce any effects

5. Now that the file has been un-registered, follow the instructions below to re-registered WSClient.dll:

   regsvr32 /i WSClient.dll

6. Once both commands have been processed successfully, reboot your PC and see if the issue is now fixed. 

5. Disable the WSRefreshBannedAppsListTask Task

What actually happens when you see the WSClient.dll is in the background there’s a task (WSRefreshBannedAppsListTask) that’s most likely calling this dependency into action at every system startup.

If none of the instructions above have allowed you to get rid of the issue, one quick and painless fix to consider is to open Task Scheduler and disable the WSRefreshBannedAppsListTask manually. 

Note: Going this route will most likely mean that the error message will disappear completely, but the drawback is that app licenses will not get resynced automatically once you disable this task. 

If you haven’t tried this fix yet and you understand the consequences, follow the instructions below to temporarily disable the WSRefreshBannedAppsListTask task and prevent the WSClient.dll from occurring again:

1. Press Windows key + R to open up a Run dialog box. 
2. Next, type ‘taskschd.msc’ inside the Run box, then press Ctrl + Shift + Enter to open up a Run dialog box.
3. At the next UAC (User Account Control) prompt, click Yes to grant admin access. 
4. Inside the Task Scheduler, expand the drop-down menu associated with Task Scheduler Library (left-hand section of the screen). 
5. Next, navigate to the following location using the same left-hand side menu:

   Microsoft > Windows > WS

6. Next, select the WS folder task folder from the left-hand section, then move over to the right-hand section pane.
   
7. Right-click on the WSRefreshBannedAppsListTask and click on Disable from the context menu. 
8. Confirm your choice, then reboot your PC and see if the problem is now fixed. 

If you always see the WSClient.dll error at every boot (immediately after the login screen), the problem is most likely caused by a remnant dependency facilitated by the WSRefreshBannedAppsListTask. 

Important: Keep in mind that even if you followed the method above to disable the WSRefreshBannedAppsListTask, a remnant dependency might still cause this behavior.

To ensure that WSRefreshBannedAppsListTask is prevented from causing this startup error, you’ll need to open an elevated CMD prompt and deploy a schtasks command that will effectively delete this task and prevent it from producing its effects. 

Here’s a quick guide on how to do this:

1. Press Windows key + R to open up a Run dialog box.
2. Next, type ‘cmd’ inside the text box, then press Ctrl + Shift + Enter to open up a Run dialog box. 
3. At the User Account Control (UAC), click Yes to grant admin access. 
4. Once you’re inside the elevated CMD prompt, type the following command to effectively delete the WSRefreshBannedAppsListTask and its unintended consequences:

   schtasks /delete /TN "MicrosoftWindowsWSWSRefreshBannedAppsListTask" /F

5. Once this command has been processed successfully, reboot your PC and see if the problem is now fixed. 

6. Clean boot

This issue can also be caused by third-party applications that interfere with the data exchange between the WSClient.dll local component and Microsoft’s servers. 

This will most commonly occur with backup tools & general resource optimization software that are way too aggressive.

Boot your computer in a clean boot mode that prevents the execution of any third-party apps or processes and see if the startup error stops occurring.

Note: This will determine whether an external service, process, or starting item is the cause of WSClient.dll startup error. 

A clean boot will force your Windows installation to boot with just the necessary Windows applications and services. Once the clean boot state is achieved, no third-party services, processes, or beginning objects will be allowed to execute.

Follow our step-by-step guide on achieving a clean boot state on Windows 10 or Windows 11. 

If the error no longer occurs while you’re clean booting, you’ve just confirmed that the problem is occurring due to a 3rd party service, process, or startup item. In this case, re-enable the previously disabled services systematically until you discover the culprit that causes the issue in your particular case. 

8. Change the DNS to Google

The WSClient.dll startup error can also be caused by an inconsistent DNS range that ends up inhibiting the connection between a WS dependency and the Microsoft servers.

This cause is much more common in Europe and Asia where ISPs (Internet Service Providers) tend to use Layer 3 nodes that end up producing a lot of network-related inconsistencies. 

Note: A layer 3 adds a header with the source and destination IP addresses to the data received from the Transport layer prior to transmission. The created packet is subsequently transmitted to the MAC or Data Link layer.

This cause is most likely applicable if you get similar errors when running other applications of games.

To fix this issue, we recommend migrating your DNS (Domain Name System) to the Google equivalent to achieve the maximum degree of stability. Even while Google Meet utilizes IPv4, we will demonstrate how to modify your IPv6 DNS range to Google’s counterparts to prevent this issue with other apps.

Here’s a quick guide on changing your DNS range to Google equivalents:

Note: The steps below are applicable on both Windows 10 and Windows 11. 

1. Pressing the Windows key + R key simultaneously will launch the Run dialog box.
   In the search box, enter “ncpa.cpl” and hit Enter to open the Network Connection window.
2. In the Network Connections box, right-click on Wi-Fi (Wireless Network Connection) or Ethernet (Local Area Connection), depending on the type of connection you’re employing.
   Note: If you have both a Wi-Fi and an Ethernet connection, make sure you choose the connection that is currently active. 
3. The next step is to choose Properties from the new menu that displays.
4. When the Properties window appears, navigate to the section titled “Networking” and then scroll down the list under “Network Connections”.
5. Scroll down until Protocol Version 4 (TCP/IPv4) appears, select the checkbox below it, and then click Properties.
6. Then, alter the Preferred DNS server to 8.8.8.8 and the Alternate DNS server to 8.8.4.4.
7. Return to the main menu and repeat the procedure for Internet Protocol Version 6: set the Preferred DNS server to 2001:4860:4860::8888 and the Alternate DNS server to 2001:4860:4860::8844.
8. Restart your computer and see if the startup error is now fixed. 

9. Run the Microsoft Safety Scanner

You should not exclude a potential malware, adware, or rootkit that is actually causing this startup error. 

If the genuine wsclient.dll has been replaced by malware that’s camouflaging as the legitimate system component, you will get this type of startup error as the functionality expected from this file is not available.

This is very likely if you receive this error whenever you attempt to download something through official Microsoft channels (for example, when installing a Windows Update or a new virus signature for Windows Defender), you should investigate the possibility of malware.

There are a number of third-party tools that may aid you with this, but most are either pricey or require you to join up for a free trial that culminates in a monthly or quarterly subscription.

Downloading the Microsoft Safety Scanner from the official website and employing it to run a system-wide scan is the finest option. However, equip yourself with patience (especially if you’re using a traditional HDD) as this tool is painfully slow and will take up most of your system resources. 

Note: Depending on the size of your normal HDD, this process might take longer than 10 to 15 hours. If you utilize an SSD, you will likely complete the task in two hours.

Here’s a quick guide on using the official Microsoft Safety Scanner to get rid of malware, adware, or rootkit that might cause this problem:

1. The first step is to download the Microsoft Safety Scanner.
   Note: Our recommendation is to download this from the official Microsoft update to ensure you’re using the latest version updated with the latest virus signatures. 
2. To begin the download, select the system-appropriate choice for your bit version of Windows.
3. After the download is complete, launch the scanner and utilize User Account Control to confirm that you want to enable modifications to be made to your computer.
4. Follow the subsequent instructions to proceed to the next screen. Be sure you pick a full scan to look for adware, rootkits, and PuPs too.

   Note: Going this route means that this procedure will take several hours to complete. Depending on whether you are using an HDD or SSD, the scanning procedure might take between two and twenty hours.

5. After the scan is complete, restart your computer and see if the wsclient.dll error is now fixed. 

10. Perform a clean install or Repair install

If none of the methods presented in this article have allowed you to address the WSClient.DLL startup error, there’s a good possibility you’re dealing with a form of system file corruption that cannot be handled routinely. In this instance, the only possible solution is to execute a sequence of commands that reset every OS component.

On top of helping you eliminate all types of file corruption that might cause the WSClient.DLL startup error, this will also re-register the file and fix the problem.

You have two options for accomplishing this: a repair install or a clean install.

• A clean install is a simple process that involves only a few mouse clicks and no installation discs. However, the biggest disadvantage is that you will likely lose the majority of your personal data (apps, games, user preferences, etc.) if they are not backed up beforehand.

• A repair install would be the most efficient method. This will require Windows 11 installation DVD that is compatible, but it will allow you to retain all of your personal components, including applications, games, user preferences, and personal media. The process will only affect the OS components, leaving the rest untouched.