update the content and add an image

Author: dessyordanova

knowledge-base/dpl-troubleshooting-nuget.md

@@ -4,7 +4,7 @@ description: Common issues that may occur when you use the Telerik NuGet server
 type: troubleshooting
 page_title: How to Fix Error 503 from Telerik NuGet Server by Migrating to NuGet v3 API
 slug: dpl-troubleshooting-nuget
-tags: error, nuget, package, installation
+tags: error, nuget, package, installation, long, wait
 res_type: kb
 ticketid: 1671187
 ---
@@ -15,25 +15,63 @@ ticketid: 1671187
 | --- | --- | ---- | 
 | N/A| Telerik Document Processing Libraries|[Desislava Yordanova](https://www.telerik.com/blogs/author/desislava-yordanova)| 
 
-## Description
-When attempting to access the Telerik NuGet server at `https://nuget.telerik.com/nuget/`, you might encounter an Error 503. This issue arises due to the deprecation of the old NuGet server and can be resolved by switching to the NuGet v3 API.
+# Troubleshooting Telerik NuGet
 
-## Cause
-The Error 503 is typically caused by the deprecation of the old NuGet v2 server at `https://nuget.telerik.com/nuget/`. Telerik encourages clients to migrate to the NuGet v3 API for enhanced performance and reliability.
+This article provides solutions to common issues that you may observe when working with the Telerik NuGet server and the NuGet packages that it provides.
 
-## Solution
-To resolve the Error 503 and ensure a more stable package management experience, follow the steps below to migrate your NuGet package source to the v3 API:
+## Issue: The NuGet Package Takes Too Long to Install or Update on Visual Studio
 
-1. Update your NuGet package source URL to `https://nuget.telerik.com/v3/index.json`.
-2. Configure the Telerik NuGet server as a package source in Visual Studio for improved package searches and restores.
+The NuGet package takes too long to install or update on Visual Studio. How to improve the installation and update times?
 
-For detailed instructions on configuring the Telerik NuGet server in Visual Studio, refer to the official documentation: [Download from the NuGet server](https://docs.telerik.com/devtools/document-processing/getting-started/installation/install-nuget-packages#download-from-the-nuget-server).
+### Solution
 
-By following these steps, you will switch to a faster, lighter, and more secure NuGet server protocol, ensuring a better package management experience.
+You can disconnect the project from the source control before running the **Update Wizard**.
+
+## Issue: Telerik NuGet Returns 401 Logon Failed after Password Change
+
+After changing your Telerik password, you get `[Telerik Nuget] The V2 feed at '...' returned an unexpected status code '401 Logon failed.'` error in the NuGet Package Manager.
+
+### Solution
+
+After changing your Telerik password, you must reset your credentials in the `NuGet.config` file. To do this, run the `NuGet Sources Update -Name "telerik.com" -Source "https://nuget.telerik.com/v3/index.json" -UserName "your login email" -Password "your new password"` command.
+
+The password must contain only ASCII characters.
+
+As an alternative, you can [reset your Telerik NuGet Feed credentials from the Windows Credentials Manager](#solution-2-windows-credentials-manager)
+
+## Issue: Unable to load the service index for source https://nuget.telerik.com/v3/index.json
+
+Make sure that the Telerik NuGet Feed is live at [https://status.telerik.com/](https://status.telerik.com/).
+
+## Issue: Resetting Telerik Nuget Credentials
+
+On Windows, if you enter and save wrong credentials for the Telerik NuGet or if you change your Telerik credentials, you won't have access to the desired NuGet packages. Before you can enter the correct user name and password, you must clear the saved credentials.
+
+### Solution 1: Resetting The Credentials in NuGet.config
+
+Try resetting your credentials by using the approach suggested in the [Telerik NuGet returns 401 Logon failed after password change](#issue-telerik-nuget-returns-401-logon-failed-after-password-change). If the credentials are not updated, continue with [Solution 2 below](#solution-2-windows-credentials-manager).
+
+### Solution 2: Windows Credentials Manager
+
+Alternatively, use Windows Credentials Manager to remove the saved credentials:
+
+1. In Visual Studio navigate to **Tools** > **NuGet Package Manager** > **Package Manager Settings**. Select **NuGet Package Manager**, click **Package Sources**, and remove the listed Telerik NuGet package source.
+1. Close Visual Studio.
+1. Open the Windows Credentials Manager. To access it, navigate to **Control Panel** > **User Accounts** > **Credential Manager**.
+1. Click **Windows Credentials**.
+1. Remove the following saved credentials:
+    * `nuget.telerik.com`
+    * `VSCredentials_nuget.telerik.com`	
+    
+	![Remove credentials from Windows Credential Manager](images/windows-credential-manager.png)
+
+1. Add the Telerik NuGet Feed again, and then enter the correct credentials. For more details, see the [Installing with Nuget]({%slug installation-nuget-packages%}) article.
+
+1. If desired, verify the NuGet credentials by inspecting the `NuGet.config` file located in `%AppData%\NuGet\NuGet.config`
 
 ## See Also
 
-- [Installing NuGet Packages](https://docs.telerik.com/devtools/document-processing/getting-started/installation/install-nuget-packages)
-- [NuGet Documentation](https://docs.microsoft.com/en-us/nuget/)
+- [Install using NuGet Packages]({%slug installation-nuget-packages%})
+- [Restoring NuGet Packages in Your CI Workflow]({%slug using-nuget-keys%})
 
 ---