Fix user account is not authorized

Error Code 0x80070057 – What is it?

Error code 0x80070057 occurs when Windows users are having problems installing updates on their machines. The error code may result due to issues affecting Windows Update, for instance, problems with system files or settings that can be accessed or modified using the registry in Windows. Error code 0x80070057 affects multiple versions of the Windows operating system including Windows 10. Common symptoms manifested when this error code and other update error codes occur include the following:

• Inability to complete the installation of updates via Windows Update
• Presence of error code message box

Error Causes

Update error codes like error code 0x80070057 occur when there are issues related to system files, programs or malicious software is present on one’s machine. To combat these issues, users may need to implement manual repair procedures, depending on the specific error code present on their device.

Solution

Further Information and Manual Repair

Windows users can fix error code 0x80070057 by manually repairing or deleting subkeys and values within the Windows registry. This enables Windows Update to function as the proper modification of settings and other information present in the registry can fix problems associated with certain error codes.

The manual repair procedures also enable users to address specific problems on the devices that may not be fixed through the use of other methods.

Method One: Back-Up Registry in Windows

The Windows registry contains information regarding applications installed on the version of Windows you use on your device. This information as well as settings related to hardware are all accessible to users and can be useful when combating problems like error code 0x80070057.

However, users will need to be very careful when making modifications within the registry in Windows. This is due to the fact that errors made while accessing the registry can lead to serious issues on your PC. Backing up your registry before you modify it is crucial since it will provide protection against any problems that may arise if you make an error. This is the first step in resolving error code 0x80070057. Follow the steps below to back up your registry properly.

• Step one: Type regedit.exe in the search box near the Start button.
• Step two: Type the appropriate password or provide confirmation if you are prompted to do so
• Step three:  Locate Registry Editor
• Step four: Select registry key or subkey that you want to back up
• Step five: Click File > Export
• Step six:  In the Export Registry File dialog box, choose a location where you will save the backup copy
• Step seven: Name the backup file then select Save.

In the case of fixing error code 0x80070057, the registry file or subkey you will need to back up relates to this: HKEY_LOCAL_MACHINE. This contains configuration details or information related to your machine regardless of the user. Also note that the registry, once you have created a backup file, will be protected, thus enabling you to move to the manual method mentioned below.

Method Two: Make Changes to the Windows Registry

The execution of modifications to the registry can be a complex procedure, especially if you are an average Windows 10 user who lacks technical knowledge. Thankfully, even non-technical users can access the solutions they need by simply following the instructions provided in this article.

You may also contact a Windows repair technician as well, in case you have trouble implementing the steps mentioned for modifying your Windows registry or if other problems arise while you are proceeding with these instructions.

Step one: Access the Windows Registry Editor by typing regedit.exe in the search box near the Start button.

Step two: Type the appropriate password or provide confirmation if you are prompted to do so

Step three:  Locate Registry Editor

Step four: Enter the following:

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsUpdateUX] "IsConvergedUpdateStackEnabled"=dword:00000000

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsUpdateUXSettings] "UxOption"=dword:00000000

After making these modifications in the Windows registry, restart your machine. You can then check Windows Update to see if the problem has been resolved. If the modifications to the registry have proven successful, you will no longer see the error code 0x80070057 message box. You will also be able to complete all updates via Windows Update.

Method Three: Download an Automated Tool

If you wish to always have at your disposal a utility tool to fix these Windows 8 and other related issues when they do arise, download and install a powerful automated tool.

Windows 10 is has a lot of features that help a user in optimizing a computer. So when the operating system encounters a problem, it is able to provide users with proper resources to get the problem fixed. There are even times when a user is not notified and an issue is either being repaired or dodged in the background. This kind of feature is known as the Diagnosis of the Automatic Repair feature that starts when your computer is booting. In such times, you will either see the “Diagnosing your PC” or “Preparing Automatic Repair” message on your screen. Although this feature is useful and has proven to be effective, some users reported that the process gets stuck. If you experience the same problem, read on as this post will guide you on what to do to fix it but before you start troubleshooting the problem, you might want to perform a Hard Boot first. All you have to do is to power down your computer, remove the battery and the AC adapter and then reconnect them. After that, tap and hold the power button for about 20 seconds and see if your computer boots up properly. If it doesn’t, follow the given fixes below.

Option 1 – Try disabling the automatic Startup Repair

The Automatic Startup Repair window will automatically open during boot when you have some system driver-related problem. So if you think that this is where the problem lies, you can try to disable the automatic Startup Repair.

• Click on Troubleshoot and go to the Advanced options.
• After that, select Command Prompt and execute the following command:

bcdedit /set recoveryenabled NO

• Restart your computer after that and then check.

Option 2 – Run the System File Checker

System File Checker or SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files to good system files that might be the cause why you’re facing this problem. To run the SFC command, follow the steps given below.

• Type “cmd” in the Start search and then right-click on the appropriate search result.
• Next, select “Run as administrator” to open Command Prompt with admin privileges.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

• Now restart your computer and see if the problem is fixed or not.

Option 3 – Run CHKDSK to check your disk for errors

When it comes to some issues concerning the hard drive or removable devices, there is a utility in Windows that might help which is called “chkdsk”. This error check utility can help with several issues in the system.

• Tap the Win + S keys to open the Search box.
• Then type “command prompt” in the field and from the search results that appear, right-click on Command Prompt and select “Run as administrator”.
• After opening an elevated command prompt, copy and paste the following command and hit Enter:

chkdsk /r /f

• Now if you are prompted to run CHKDSK after your reboot your computer, just tap Y and reboot your PC.
• If CHKDSK is not able to find any errors, tap the Win + E keys and navigate the access window. From there, right-click on the concerned drive and click on Properties.
• After opening Properties, click on the tab Tools and then click on the “Check” button under the Error-checking section.
• Wait until the process is completed and then restart your computer.
• Once your computer has restarted, try accessing the file and check if the error persists.

Option 4 – Run the DISM tool

The next thing you can do is run the DISM tool. This tool is known to repair potentially corrupted files in your system as having them could also system issues like your computer getting stuck in the “Diagnosing your PC” or “Preparing Automatic Repair” screen.

• Tap the Win + X keys and click on the “Command Prompt (Admin)” option.
• After that, input each one of the commands listed below sequentially to execute them:
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-Image /RestoreHealth

• Once you’ve executed the commands given above, restart your computer and check if the problem is now fixed.

Option 5 – Try to use installation media to boot and repair your computer

Another thing you can try to resolve the issue is to use the Windows installation bootable media so you can boot and repair the operating system. To use it, follow these steps:

• You need to first create an installation media which has the dame version of the operating system installed in your computer.
• After that, once you reach the Install Windows screen, click on the “Repair your computer” link.
• Wait until the repair is completed and then shut down your computer
• Now once your computer has restarted, check if it can now boot properly.

Resource hogging is a term when one single application or few of them are taking all system resources for themself causing extreme slow down in the computer and nonresponsiveness. It can be a very frustrating and time-consuming experience and it can cost you money if you can not finish work on time due to this effect. I believe that everyone has experienced at least one slowdown in their IT carrier because of resource-hogging applications and most users do not know how to deal with this. We are here to help you with this issue. Just to be aware that this method shown here is not a method to miraculously speed up your PC or anything similar, this is to be able to detect and recover from extreme slowdowns. Hardware components are still very important and if you can upgrade your computer if it is outdated, please do it because new applications will require a more modern system, and not any kind of tips and tricks will save you from outdated hardware.

Identifying resource hogging app

Now when we got that out of the way let's talk about slowdowns, it is no secret that sometimes an application has bugs and memory leaks that can cause this kind of behavior, and sometimes the application simply takes up too much memory for any other application to work normally. The most simple and straightforward way is to bring up a Windows task manager and inspect running applications and services. You can bring task manager by the key combination of CTRL + SHIFT + ESC If the system is in deep memory deficit you will have to wait for the task manager to open and show itself on-screen. Once opened, click on more details if that view is not opened by default. Once the view expands you will see all running applications with how much RAM memory have they taken and how much CPU they are using.

What to do with app?

Now you are presented with a choice on what to do with the problematic application. If you press the end task button on the bottom right, Windows will kill the application and its processes but any unsaved work inside the application will be lost and unrecoverable in most cases. Or you can try to remove smaller applications running to free up more memory and CPU in order for the computer to catch up. Any choice you make is up to you, but be very careful not to kill Windows essential service by mistake, that will cause immediate system instability with high chances of a system crash.

If you encounter the MUP_FILE_SYSTEM Blue Screen error with a value of 0c00000103, then it indicates that the multiple UNC provider or MUP has got an invalid of unexpected data. This can lead to the fact that the MUP cannot channel a remote file system request to a network redirector, the UNC, or Universal Naming Convention provider. There are several ways you can fix the MUP_FILE_SYSTEM Blue Screen Error on your Windows 10 computer, you can try to check the hardware of your computer physically, update or rollback some device drivers, run the Driver Verifier Manager, remove any hardware you’ve installed recently or fix issues related to IRQ. Use the given options below as reference to fix the MUP_FILE_SYSTEM Blue Screen Error.

Option 1 – Try to physically check the hardware

The first thing you can do is to check the physical status of the hardware in your computer. You can clean the dust off the hardware components like the Network Card of the computer. You might want to use a small blower or you could also use a soft cloth and run the components gently. Make sure that you don’t damage any parts with moisture or cause harm to any circuits while you carry out this task.

Option 2 – Try to rollback, update several device drivers

You can try to roll back, update or disable certain device drivers on your computer to resolve the MUP_FILE_SYSTEM Blue Screen error.

• First, boot your computer into Safe Mode.
• After that, tap the Win + R keys to launch Run.
• Type in devmgmt.msc into the box and tap Enter or click OK to open the Device Manager.
• After that, a list of device drivers will be displayed. From there, look for the device drivers related to the Network Card, Chipset, Disk Drive, and the Graphics Drivers and any other driver related to MUP.sys and SwapBuffers.sys system files
• After that, right-click on each entry of the device drivers and select the “Update Device” option from the menu.
• Now follow the next on-screen instructions that appear and then restart your computer.
• After restarting your computer, check if the Stop error is now fixed.

Option 3 – Configure the Driver Verifier Manager

The Driver Verifier Manager is another tool in Windows that could help you fix driver-related issues. And so if you want to fix the MUP_FILE_SYSTEM Blue Screen error you need to use the Driver Verifier Manager:

• Type in the keyword “Verifier” in the Cortana search box to search for Verifier in Windows 10.
• After that, select the option “Create custom settings”.
• Make sure that you have checked everything except the options “DDI compliance checking” and “Randomized low resources simulation”.
• Next, select the option “Select driver names from a list” option.
• Afterward, you have to select all the drivers from any unofficial or third-party provider. To simply put it, you have to select all the drivers that are not supplied by Microsoft.
• Then click on the Finish button.
• Open Command Prompt as administrator and execute this command – verifier /querysettings
• The command you just executed will display the Driver Verifier settings so if you see any of the flags enabled boot your Windows 10 PC into Safe Mode.
• Open the Command Prompt as admin again and run this command – verifier /reset
• The command will reset the Driver Verifier. Once the process is done, restart your PC and check.

Option 4 – Try to disconnect or disable newly installed hardware

In this option, you will have to disable or remove the hardware you’ve just installed recently since external devices could be the one that’s causing the Blue Screen of Death error to appear. To do that, just disconnect any external device that’s connected to your computer physically and then check if it fixes the MUP_FILE_SYSTEM Blue Screen error.

Option 5 – Try fixing IRQ-related issues

The Stop error might have something to do with an issue related to IRQ. You can verify it by switching your PCI Cards around. Aside from that, you can also check if the IRQ2 is assigned to a COM Port that is unavailable at that time.

Option 6 – Run the Blue Screen Troubleshooter

The Blue Screen troubleshooter is a built-in tool in Windows 10 that helps users in fixing BSOD errors like MUP_FILE_SYSTEM. It can be found in the Settings Troubleshooters page. To use it, refer to these steps:

• Tap the Win + I keys to open the Settings panel.
• Then go to Update & Security > Troubleshoot.
• From there, look for the option called “Blue Screen” on your right-hand side and then click the “Run the troubleshooter” button to run the Blue Screen Troubleshooter and then follow the next on-screen options. Note that you might have to boot your PC into Safe Mode.

Option 7 – Perform a System Restore

Performing System Restore might help you in fixing the Blue Screen error. You can do this option either by booting into Safe Mode or in System Restore. If you are already in the Advanced Startup Options, just directly select System Restore and proceed with the next steps. And if you have just booted your PC into Safe Mode, refer to the steps below.

• Tap the Win + R keys to open the Run dialog box.
• After that, type in “sysdm.cpl” in the field and tap Enter.
• Next, go to the System Protection tab then click the System Restore button. This will open a new window where you have to select your preferred System Restore point.
• After that, follow the on-screen instructions to finish the process and then restart your computer and check if the problem is fixed or not.

What Is Runtime Error R6034?

Runtime Error r6034 is one of the most commonly occurring errors.  This error usually arises in Windows Vista and Windows 7. The message that appears to the user states ‘An application has made an attempt to load C runtime library incorrectly, please contact the support team for more information’. As the message suggests, this problematic error occurs simply because an application attempts to load the C runtime library without a manifest.

Solution

Error Causes

Runtime Error r6034 occurs when the system compiler fails to compile the working application. While this is the primary reason, there are some other conditions that trigger Runtime Error r6034 which are outlined below.

• Existence of viruses and malware in the system.
• Corrupt or missing system files.
• Power outages.
• Hardware problems.
• Hardware driver problems.

There are several other reasons that may trigger Runtime Error r6034 that are beyond the scope of this article. Regardless of what triggers this error, it is crucial to ensure that it is fixed as soon as possible.

Further Information and Manual Repair

There are several ways to deal with Runtime Error r6034. However, one of the most effective ways is listed below as follows.

• When this error occurs, restart your computer. Make sure you press F8 before the windows logo is displayed.
• Choose safe mode and press enter.
• Go to the ‘Start’ button and type ‘msconfig’ in the search box. Press enter.
• The MSConfig program will now open.
• Choose ‘Start up’ in the general tab and then click on the ‘Load Start Up’ item.
• Click on the ‘Services’ tab. Now click ‘Hide all Microsoft Services’ and then choose ‘Disable All’.
• Close the system configuration window.
• Restart the computer.

After restarting your computer, you will notice that the Runtime Error r6034 has been removed. If this approach fails to deliver the desired results, it is advised to follow the steps listed below.

• Go to the start button. In the search box, type ‘System Restore’.
• When System Restore appears, click on it.
• The system restore window will open. Make sure any process or application that’s open is now closed.
• In the System Restore window, if a calendar list appears, it means the restore point is open. Now choose the point from where the error appeared and click Next.
• This process may take some time. Your system will restart automatically and the Runtime Error r6034 will disappear.

In case you don’t know, the Windows Registry contains a System Hive which is a core part of Windows. The Windows operating system store various settings, options, and configurations. And if you encounter a Device Manager Error 49 for a device then it means that the system hive has exceeded its size limit. Worry not for this post will provide you with possible solutions that can help you in fixing error code 49. You will see the following error message when you encounter error code 49:

“Windows cannot start new hardware devices because the system hive is too large (exceeds the Registry Size Limit), (Code 49)”

There are instances when it may so happen that the device or devices are no longer attached to the computer but they are still listed in the system hive of the registry. For instance, if you were removing hardware and application for years but they weren’t removed from the registry then the size of the system hive keeps on growing until it hits the maximum limit. As you know, making changes in the registry manually, no matter how knowledgeable you are on such things is not sage since the registry is not only important but also complex. In addition, the System Hive is also a permanent part of the Registry associated with a set of files that contain information related to the configuration of the computer on which the OS is installed. To resolve this error, you must remove or uninstall any hardware devices that are no longer in the system. In fact, the Device Manager hides them by default so you need to enable hidden or non-present devices. Follow the instructions given below to set the Devices Manager to display devices that are no longer connected to the computer. Step 1: Tap the Win + R keys to open the Run dialog box. Step 2: After that type in “cmd” and hit Enter to open the Command Prompt. Step 3: Type “set devmgr_show_nonpresent_devices=1” in the Command Prompt and hit Enter to enable the hidden devices option. Step 4: After that, exit Command Prompt and tap Win + X + M to open the Devices Manager. Step 5: After opening the Devices Manager, click on View and then select the “Show hidden devices” option. This will show you all the devices that are not connected to the computer but are still mentioned. Step 6: Next, select a non-present device and click Uninstall from the Driver tab. Step 7: After that, repeat what you’ve done on step 5 for any other device that you no longer use. Step 8: Restart your computer. You can check the device Properties dialog box in the Device Manager after you’re done removing all the useless devices, to check if the error is now fixed or not. Moreover, you can also try running the Hardware and Devices Troubleshooter as it can also help resolve hardware-related problems. To use it, refer to the steps below.

• The first thing you need to do is click on Start and then on the gear-like icon to pull up the window for Settings.
• After opening Settings, look for the Update and Security option and select it.
• From there, go to the Troubleshoot option located on the left-hand side of the list.
• Next, select Hardware and Devices from the list and open the Troubleshooter and run it. Once it is doing its job, wait for it to complete the process and then restart the system.
• After the system restarts, check if the problem’s now fixed. If not, refer to the next option given below.

One of the most common ways cybercriminals use to inject suspicious code into devices is by tricking users into installing a malicious program on a targeted device. Oblivious users are vulnerable to such tricks, which is why Microsoft has been working hard in the background to address this issue. Recently, Microsoft announced the availability of a sandboxed version of Windows 10 that runs inside Windows 10 in order to isolate suspected software to run inside it and protect the system from potential threats. This Windows Sandbox feature is a new feature that keeps your computer secure. It is a virtual disposable environment that you can enable. So if suspect any software of being malicious, you can run this software in an environment and ensure that it won’t interfere with any normal processes and would not jeopardize files on your computer. To simply put it, “Windows Sandbox is a new lightweight desktop environment tailored for safely running applications in isolation”. So if the Sandbox is closed, all the residual files, software, and other data are deleted permanently. To enable Windows Sandbox, refer to the instructions provided below. Step 1: You have to make sure that you are running either Windows 10 Enterprise Editions or Windows 10 Pro and that your computer is running build 18305 or newer. Step 2: After that, you have to enable Virtualization to let another instance of Windows 10 running in Sandbox mode. Step 3: Next, search for Windows Features on and off in the search box and then select the appropriate entry. Step 4: From the list, go to the mini window and check the Windows Sandbox and then click on OK. Step 5: Afterwards, in the Cortana Search box, search for “Windows Sandbox” and select the related entry to run it in an elevated window. Step 6: Then from your main computer (host), copy the executable file and paste it inside the Windows Sandbox environment. Step 7: Now run the executable file in the Sandbox environment and use it as you normally do. Step 8: Once you’re done, close the Windows Sandbox application and as mentioned, every data regarding the executable file and the temporary environment will be deleted. Step 9: And for the sake of safety, ensure that there are no modifications made to the host because of the executions in the Sandbox environment. You have the option to contact Microsoft for feedback related to Windows Sandbox. You can use the traditional Feedback Hub if you have any suggestions or any issues. Just fill in the appropriate details and select Windows Sandbox for the feature category under the Security and Privacy section. And if you have any issues related to the execution of and within Windows Sandbox, simply choose “Recreate my problem” then select Start capture to reproduce the issue, and once you’re done, select Stop capture.

The third time is charm saying goes but not when we are talking about Microsoft. Print spooler is again in focus, in a bad way. This is the third print spooler vulnerability to emerge in just five weeks. While a critical flaw was originally identified and patched in June, a similar flaw came to light shortly after and was subsequently patched (with mixed success). Microsoft is once again advising its customers to disable Windows print spooler after a new vulnerability that allows hackers to execute malicious code on machines has emerged. While a patch fixing the flaw will be released in due course, the most effective workaround currently on the table is to stop and disable the print spooler service entirely.

"An elevation of privilege vulnerability exists when the Windows Print Spooler service improperly performs privileged file operations. An attacker who successfully exploited this vulnerability could run arbitrary code with SYSTEM privileges. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights."

Stop this service right away or you are risking a potential attack.

1. Press ⊞ WINDOWS + X to open the hidden menu
2. Click on Power Shell (admin)
3. In Power Shell type in the following command to check if spool service is running: Get-Service -Name Spooler followed by ENTER
4. If spooler service is running type in the next command to stop it: Stop-Service -Name Spooler –Force and press ENTER
5. Then follow with this command to disable it at startup: Set-Service -Name Spooler -StartupType Disabled followed with ENTER

That’s it, we hope a patch will come soon for all the people that are using network printing and indeed need this service running in order to do work.

Error 0xA00F4244 or 0x200F4244 is when Windows can not detect the WEB camera in your system and it is usually accompanied by the message: We can’t find or start your camera. There could be several reasons for this error and in this guide, we will cover all of them in order to help you to get back on track and start using your WEB camera which is perhaps now more required than ever in this world we live in.

1. Check privacy settings

   With the latest Microsoft Windows updates come the latest issues and it is not strange that privacy settings can become reset or changed when an update is applied. This is a quick fix to this issue and can be the sole reason why you get this error, go to Windows settings, then to privacy and check to see if the WEB camera is turned OFF, if this is the case turn it back ON and make sure that option Allow apps to access your camera is also set to ON.

2. Check if the camera is enabled

   Sometimes it is by mistake, sometimes by an update but the web camera could be disabled in the device manager of Windows. Right-click on the Windows Start button and click on device manager to open it up, find and expand the cameras category. Right-click on your camera, if it is disabled, you will have the option to enable the camera, if it is enabled and Windows is detecting that it is working fine you will have the option to disable it.

3. Check antivirus settings

   Antivirus and firewall applications are in today's world and life-essential piece of software but they can sometimes create more harm than good, from stopping windows updates to killing important services of applications and preventing internet access being just some examples of their paranoid behavior. Try disabling or turning your protection software OFF and see if your WEB camera will miraculously come back to life. If this is the case, somewhere in the settings of software there is an option that controls this aspect, try to locate it and set it in that way so you are able to use your camera.

4. Reinstall camera driver

   If the previous three solutions failed to produce a satisfactory solution then reinstalling the camera driver might fix the problem. Go to your manufacturer's camera website and download the latest driver for your camera. Go to the device manager and uninstall the driver for the camera, then apply the latest driver and reboot the system.

5. Check connections and cable

   Sometimes an issue is not due to software nature, sometimes it is hardware. Try checking connections and plug the camera in another USB port, twist and turn the cable a little to see is issue cable-related.

6. Check to see if the application supports your camera

   If Windows has detected the camera and is not reporting any issues with it check your application to see if it can detect your camera and that it supports it fully. Sometimes newer applications tend to support only newer camera models. Try to use the camera in other software as well to see if the problem is with the application you are using.

7. Try camera on another computer

   If everything else fails, try the camera on another computer to see if it will work there. If the camera is not working there as well it is probably malfunctioned and broken for good. If it does work there, try to find out what is different in that computer in comparison to yours, maybe it is some service running in the background, certain application configuration, Windows version itself, USB port version, or something else.

Skinning of applications is not new to PC users, but did you knew you could skin Steam? With skin, you can customize the UI and style of the client to what you want making it more personal and to your liking. First thing is to find the skin that you would like to install. There are a lot of sites where you could find custom made Steam skins but we would recommend steamskins.org The site itself is organized in tabs with different sections, once you click on the tab you will get a list of skins available for chosen section. If you click on the skin you will be taken to skin page detail where you can find what skin is aiming for, its legibility, a record of how the skin has been altered over time, or some mix of these aspects. Note that some skins might have issues like some buttons might be missing from big picture mode but so far none of the skins has any kind of client breaking feature, only functionality one.

Downloading skin

Once you have chosen desired skin and while on the skin details page, scroll to the middle of the page just above the Related Skins sections with two options: Direct Download and External Download. Now usually I would recommend Direct download but in this case, I would advise going with External Download for the simple reason that the External link will send you to the developer's website where there is a higher chance to get the latest updated skin.

Installing it in Steam

Once the skin is downloaded you will first need to create a skin folder inside your Steam installation location. Navigate to your Steam installation folder (default: C:\Program Files (x86)\Steam) and create a new folder inside it. Give new folder name Skins and confirm. Extract the skin zip file in the newly made folder. Once the file is extracted you can delete the ZIP file if you wish. Go to your Steam client and go to Steam>Settings. In settings select Interface on the left bar and on the right part then click the Select the skin you wish Steam to use the drop-down menu and select the skin that you wish to use. Confirm and restart your Steam client

Reverting to old skin

If you found skin unappealing or, unfortunately, has some functions missing you can always choose another skin or revert back to default Steam skin. Default Steam skin is named in the drop-down menu as < default skin >.