

- #WINDOWS CMD REGISTRY REPAIR HOW TO#
- #WINDOWS CMD REGISTRY REPAIR WINDOWS 10#
- #WINDOWS CMD REGISTRY REPAIR CODE#

Please specify the setup file: ActiveXFix.cmd.Please specify the source folder: C:\Users\digit\OneDrive\Work\Intune Source\ActiveX Reg Fix\Source.Enter SOURCE path where you have stored the.Run the IntuneWinAppUtil.exe tool from Command prompt.You need to paste the tool into the “ Intune Source” folder that you created above. Now you need to create an IntuneWin package using the tool called IntuneWinAppUtil.exe. Paste ActiveXFix.reg and ActiveXFix.cmd files into the above folder.Create a folder called Intune Source\ActiveX Reg Fix\ Package.Create a Folder called Intune Source\ActiveX Reg Fix\Source.Before proceeding further, create a folder structure to store the source files and package files.
#WINDOWS CMD REGISTRY REPAIR WINDOWS 10#
This helps to deploy the registry fix to Windows 10 or 11 Azure AD joined PCs using Intune. Regedit.exe /s 1.0>C:\Windows\Temp\ActiveXFix\Ver1.0.txtĭownload the IntuneWinAppUtil.exe to covert the files created above into the IntuneWin package. You will need to paste the following registry information to a notepad and save it as ActiveXFix.reg file.Ĭopy "%~dp0*.reg" C:\Windows\Temp\ActiveXFix /Y The first file is the registry file itself. You need to create two files to deploy registry fix using Intune. Create IntuneWin Package to Deploy Registry Fix I think Intune remediation script method is much better if you have appropriate licenses.

I will cover that later in a different post. You can also use a remediation script to deploy registry fixes using Intune. This client agent is created by Intune team only for IntuneWin application deployments. IntuneWin app installation is handled by a new agent called Intune Management Extension. But in this post, I’m going to cover Intune method for Azure AD joined Windows 10 PCs. You can use the best option suited for your organization. There are other methods also to fix the vulnerability, like group policy. Microsoft provided a registry file to fix this vulnerability with the office application. It’s time to fix the CVE-2021-40444 issue using Intune registry fix method.
#WINDOWS CMD REGISTRY REPAIR CODE#
I have already posted a fix for the new remote Code Execution Vulnerability in the MSHTML component using SCCM.
#WINDOWS CMD REGISTRY REPAIR HOW TO#
Type the following command to enter into the System32 folder and press Enter: cd d:\windows\system32Ĭhange D in the command with the correct drive letter for your scenario.Let’s learn how to Deploy Registry Fix using Intune Win32 app. You are in the correct drive letter if you see the Windows folder. Type the following command to confirm you are in the correct drive to restore the Registry and press Enter: dir Command Prompt in Advanced startup

As a result, type the following command to enter into the correct drive where Windows 10 is installed and press Enter: d:\ However, in most cases, the drive letter is D:\. Although the OS resides on the C:\ drive, this drive letter could change to something else when you boot your computer on recovery mode. This means that you’ll now need to move to the drive letter where Windows is installed. When the device starts in Command Prompt, it will start on X:\Windows\System32.
