--- title: Hotfix Instructions - Kentico 8.2 --- > Agent instructions: > **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown. > > - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version. > - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt). Hotfixes allow you to fix problems in your installation of Kentico. You can download hotfix packages and view the list of fixed bugs on the [Kentico DevNet portal](http://devnet.kentico.com/download/hotfixes). > **Info:** If you have the source code version of Kentico, please see [Hotfix Instructions - Kentico 8.2 Source Code](https://docs.kentico.com/k82/installation/hotfix-instructions-kentico-8-2/hotfix-instructions-kentico-8-2-source-code.md). > **Note:** **Note** > > Hotfixes are not tested for all possible scenarios, so you may experience issues after applying the hotfix. > > Always **backup your project files and database** before applying a hotfix. ## Table of Contents ## Prerequisites You can only apply the hotfix to complete Kentico projects that use the standard folder structure (the solution file, _GlobalAssemblyInfo.cs_, the _CMS_ and _Lib_ sub-folders). If you run your website as a deployment of the CMS folder, you need to hotfix the original complete project and then create a new deployment. ## Applying the hotfix to web site projects ### Local installation 1. If your system stores virtual objects on the file system (due to enabled [Deployment mode](https://docs.kentico.com/k82/deploying-websites/deployment-mode-for-virtual-objects.md) or source control options), return the files to the database. You can re-enable deployment mode or source control after you apply the hotfix. 2. Run **Kentico Hotfix Utility (Hotfix.exe)** from the location where you installed the hotfix. 3. Select your project folder using the **Browse** button or type in the path to the project manually. 4. Use the application to back up your project files and/or database if you haven’t already done so. 5. Select which components you want to update. Click **Switch to advanced mode** if you wish to change the settings. We recommend updating all components. - **Kentico files** - the files of your web project - **Setup files** - the Kentico installer and external utilities (which are separate from the web project) - **SQL script** - the database structure and data 6. Choose a method of taking the project offline and back online. 7. Click **Next** to start the update procedure. 8. After the update finishes, click **Next** to view any problems that may have occurred and the instructions to solve them. For more information, see [Kentico Hotfix and Upgrade Utility](https://docs.kentico.com/k82/external-utilities/kentico-hotfix-and-upgrade-utility.md). ### Remote installation If you cannot access your web project directly (for example when the project is located on a remote hosting server), you can use the Hotfix Utility to create the updated file structure and then upload them to your web project location.  1. Navigate to the location where you installed the hotfix. 2. Run **Hotfix.exe** from the command line with the **/deploy** parameter. Set the parameter value based on the installation type you’re using: - **net40site** - web site project using .NET version 4.0 - **net45site** - web site project using .NET version 4.5 **Example**: _Hotfix.exe /deploy=net40site_ This launches the Hotfix Utility, which then creates the files and folders necessary for updating a project running on .NET version 4.0 and saves them into the folder chosen in the first step of the Hotfix Utility wizard. Additionally, you can provide the **/path** parameter, which tells the application where to create the file structure. This way you won’t have to set the path in the first step of the Hotfix Wizard. You can supply the **/path** parameter in two different formats — **relative**, which represents a folder in the location from which the utility was executed; or **absolute**, which can be any path to a local disk. **Example**: _Hotfix.exe /deploy=net40site /path=Deploy_ This launches the Hotfix Utility, which then creates a folder named _Deploy_ in the directory from which the utility was executed and copies all files and folders necessary for updating a project running on .NET version 4.0 into that folder. 3. Once you have the update files ready, take your website offline. You can do this by copying the **App\_Offline.htm** file from the hotfix installation directory into the root of the remote web project. 4. Upload the update files created by the Hotfix Utility into your remote web project's **CMS** folder (overwrite the original files). > **Note:** **Important** > > If you have previously modified some of the Kentico project files (such as web parts or administration interface files), DO NOT OVERWRITE these files. You could lose your modifications. > > You need to compare the modified files with the new versions and make appropriate changes manually. 5. Manually execute the hotfix SQL scripts on your Kentico database. - If you do not use separated databases - run the **Hotfix\_separated.sql**and **Hotfix\_default.sql** script files located in the **SQL** folder of your hotfix installation directory. We recommend running the files in the described order. - If you use [separated databases](https://docs.kentico.com/k82/on-line-marketing-features/contact-management/separating-the-contact-management-database.md) - run the **Hotfix\_separated.sql** script file on the separated database and **Hotfix\_default.sql** on your main database. The script files are located in the **SQL** folder of your hotfix installation directory. 6. Bring your website back online (delete the **App\_Offline.htm** file). ## Applying the hotfix to web application projects ### Local installation 1. If your system stores virtual objects on the file system (due to enabled [Deployment mode](https://docs.kentico.com/k82/deploying-websites/deployment-mode-for-virtual-objects.md) or source control options), return the files to the database. After you apply the hotfix, re-enable deployment mode or source control and rebuild the project. 2. Run **Kentico Hotfix Utility (Hotfix.exe)** from the location where you installed the hotfix. 3. Select your project folder using the **Browse** button or type in the path to the project manually. 4. Use the application to back up your project files and/or database if you haven’t already done so. 5. Select which components you want to update. Click **Switch to advanced mode** if you wish to change the settings. We recommend updating all components. - **Kentico files** - the files of your web project - **Setup files** - the Kentico installer and external utilities (which are separate from the web project) - **SQL script** - the database structure and data 6. Choose a method of taking the project offline and back online. 7. Click **Next** to start the update procedure. 8. After the update finishes, click **Next** to view any problems that may have occurred and the instructions to solve them. 9. Open the project solution in Visual Studio and build the solution. For more information, see [Kentico Hotfix and Upgrade Utility](https://docs.kentico.com/k82/external-utilities/kentico-hotfix-and-upgrade-utility.md). ### Remote installation If you cannot access your web project directly (for example when the project is located on a remote hosting server), you can use the Hotfix Utility to create the updated file structure and then upload them to your web project location.  1. Navigate to the location where you installed the hotfix. 2. Run **Hotfix.exe** from the command line with the **/deploy** parameter. Set the parameter value based on the installation type you’re using: - **net40app** - web site project using .NET version 4.0 - **net45app** - web site project using .NET version 4.5 **Example**: _Hotfix.exe /deploy=net40app_\ This launches the Hotfix Utility, which then creates the files and folders necessary for updating a project running on .NET version 4.0 and saves them into the folder chosen in the first step of the Hotfix Utility wizard. Additionally, you can provide the **/path** parameter, which tells the application where to create the file structure. This way you won’t have to set the path in the first step of the Hotfix Wizard. You can supply the **/path** parameter in two different formats – **relative**, which represents a folder in the location from which the utility was executed; or **absolute**, which can be any path to a local disk. **Example**: _Hotfix.exe /deploy=net40app /path=Deploy_\ This launches the Hotfix Utility, which then creates a folder named _Deploy_ in the directory from which the utility was executed and copies all files and folders necessary for updating a project running on .NET version 4.0 into that folder. 3. Once you have the update files ready, take your website offline. You can do this by copying the **App\_Offline.htm** file from the hotfix installation directory into the root of the remote web project. 4. Upload the update files created by the Hotfix Utility into your remote web project's **CMS** folder (overwrite the original files). > **Note:** **Important** > > If you have previously modified some of the Kentico project files (such as web parts or administration interface files), DO NOT OVERWRITE these files. You could lose your modifications. > > You need to compare the modified files with the new versions and make appropriate changes manually. 5. Manually execute the hotfix SQL scripts on your Kentico database. - If you do not use separated databases - run the **Hotfix\_separated.sql**and **Hotfix\_default.sql** script files located in the **SQL** folder of your hotfix installation directory. We recommend running the files in the described order. - If you use [separated databases](https://docs.kentico.com/k82/on-line-marketing-features/contact-management/separating-the-contact-management-database.md) - run the **Hotfix\_separated.sql** script file on the separated database and **Hotfix\_default.sql** on your main database. The script files are located in the **SQL** folder of your hotfix installation directory. 6. Open the project in Visual Studio and build the solution. 7. Bring your website back online (delete the **App\_Offline.htm** file). ## Applying the hotfix to Microsoft Azure In the case of websites hosted on Microsoft Azure, you need to apply the hotfix to your local copy of the web application and then redeploy. 1. Run **Kentico Hotfix Utility (Hotfix.exe)** from the location where you installed the hotfix. 2. Select the folder containing your local version of the project using the **Browse** button or type in the path to the project manually. 3. Use the application to back up your project files and/or database in case you haven’t already done so. 4. Select whether you want to update files, database or both. If your database is hosted on SQL Azure, you need to update it manually. 5. Click **Next** to start the update procedure. 6. After the update finishes, click **Next** to view any problems that may have occurred and the instructions to solve them. 7. Open the project’s solution in Visual Studio and rebuild it. 8. Redeploy the application to Microsoft Azure. 9. If your website’s database is hosted on SQL Azure, manually execute the hotfix SQL scripts against it. - If you do not use separated databases - run the **Hotfix\_separated.sql**and **Hotfix\_default.sql** script files located in the **SQL** folder of your hotfix installation directory. We recommend running the files in the described order. - If you use [separated databases](https://docs.kentico.com/k82/on-line-marketing-features/contact-management/separating-the-contact-management-database.md) - run the **Hotfix\_separated.sql** script file on the separated database and **Hotfix\_default.sql** on your main database. The script files are located in the **SQL** folder of your hotfix installation directory. ## After applying the hotfix All users who work with the Kentico administration interface should **clear the cache** in their browsers after applying the hotfix. Otherwise, some features in the administration interface may not be displayed correctly. ## Updating setup files and external utilities Hotfixes provide bug fixes for all files related to the Kentico installation, which includes the installer and other external utilities, such as Kentico Installation Manager, Kentico Service Manager or the Kentico AD Import Utility. To update these files and utilities, you need to apply the hotfix to the setup files: 1. When running the hotfix utility, click **Switch to advanced mode** in the **Change confirmation** step. 2. Select the **Setup files** checkbox. 3. Click **Next**. 4. In the **Running applications** step, stop any applications that are currently running from the setup files. 5. Click **Next** and continue through the rest of the hotfix procedure. The hotfix makes any required changes to the files in the directory where you installed your Kentico setup files. ## Additional notes and workarounds ### General - Marketing automation - When configuring the _'Set contact property_' marketing automation action, the _'Property name'_ selector contains unnecessary contact columns. To hide the columns, edit the _Set contact property_ action on the Actions tab of the Marketing automation application and disable the _'Show all columns'_ option for the _PropertyName_ parameter. - Dancing Goat sample site - The comparison of the password and password confirmation fields in the user registration form on the sample Dancing Goat was not case sensitive. Follow the steps below to resolve the problem: 1. Open the **Modules** application. 2. Edit the **Membership** module. 3. Select the **Classes** tab and edit the **User** class. 4. On the **Alternative forms** tab, edit the **User Registration (Dancing Goat)** form. 5. Select the **UserPassword** field and click the existing **Validation rule**. 6. Change the validation rule type to _**General condition**_. 7. Copy the following macro code into the **Enter text** field: _Value == Fields\["PasswordStrength"].Value|(casesensitive)true_ 8. Click **Apply** and then **Save** the entire field. ### 8.2.4 - Reporting - Hotfix 8.2.4 updates and overwrites the **Proc\_Analytics\_Pivot** stored procedure. If you have customized this stored procedure, you need to manually apply your changes again after installing the hotfix. ### 8.2.13 - On-line forms - Hotfix 8.2.13 updates the generating of autoresponder and notification emails of forms to ensure HTML validity. For the changes to take effect, you need to manually resave the settings on the **Email notification** and **Autoresponder** tabs of your forms in the **Forms** application. ### 8.2.27 - The Contact import functionality now enables the 'Track activities' property for imported contacts. If you've used Contact import before applying this hotfix and want the imported contacts' activities tracked, you need to enable the property manually. ### 8.2.29 - The **CategoryOrder** column in the **CMS\_PageTemplateCategory** database table is no longer used by the system and the hotfix sets its values to NULL. - Culture dependent data used in the **Property** value of the **Set contact property** marketing automation action must always be entered in the 'en-US' culture format. For example, use the MDY format for dates (12.21.1989). ## Fixed bugs For a full list of bugs covered by the hotfix, open the [Hotfixes page](http://devnet.kentico.com/download/hotfixes) on DevNet and click **Fixed bugs** for the appropriate Kentico version.