Regkeys haven't been added when running Test-D365FOConfiguration.ps1

When we run step 9.3 to deploy an On-Premise environment, sometimes we might face this error

Issue: the Regkeys haven't been added
Solution: simply we just need to run the Powershell script  .\Configure-PreReqs.ps1 -MSIFilePath <\Tools>  in order to reinstall the tools for the server

PS Microsoft.PowerShell.Core\FileSystem::\\dc\share\InfrastructureScripts-206403\VMs\aos1> .\Test-D365FOConfiguration.ps1Checking all prerequisites ...
Validating Pre-Reqs for [AOS] in this machine...
All of the expected firewall rule names were found.
Querying Machine for list of currently Installed applications
Found application Microsoft Access Database Engine 2010 Redistributable (>=14.0.7015.1000).
Found application SQL Server Management Studio 2016 SP1 (>=13.0.4001.0).
Found application Update for Visual C++ 2013 and Visual C++ Additional Runtime (>=12.0.40660).
Found application Microsoft ODBC Driver 17.2.for SQL Server (>=17.2.0.1).
Found application Microsoft ODBC Driver 13.1 for SQL Server (>=13.1.4001.0).
Windows feature .NET Framework 3.5 Features is installed
Windows feature .NET Framework 4.6 Features is installed
Windows feature Windows Process Activation Service is installed
Windows feature Internet Information Services is installed

Stop-D365FOServices : The following services still need to be stopped/disabled:
[WAS], [W3SVC]
At \\dc\share\InfrastructureScripts-206403\VMs\aos1\Configure-PreReqs.ps1:236 char:2
+     Stop-D365FOServices -ServiceNames $disabledServiceNames -Test:$Te ...
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Stop-D365FOServices
Register-D365FOStrongName : The following RegKeys haven't been added in order to disable strong name verification:
[HKLM:\SOFTWARE\Microsoft\StrongName\Verification\*,a7cf325ee2c8a9ff],
[HKLM:\SOFTWARE\Microsoft\StrongName\Verification\*,31bf3856ad364e35],
[HKLM:\SOFTWARE\Microsoft\StrongName\Verification\*,b03f5f7f11d50a3a],
[HKLM:\SOFTWARE\Wow6432Node\Microsoft\StrongName\Verification\*,a7cf325ee2c8a9ff],
[HKLM:\SOFTWARE\Wow6432Node\Microsoft\StrongName\Verification\*,31bf3856ad364e35],
[HKLM:\SOFTWARE\Wow6432Node\Microsoft\StrongName\Verification\*,b03f5f7f11d50a3a]. Run the script again to disable strong name verification.
At \\dc\share\InfrastructureScripts-206403\VMs\aos1\Configure-PreReqs.ps1:239 char:2
+     Register-D365FOStrongName -StrongNameDisabled $strongNameDisabled ...
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Register-D365FOStrongName
Register-UAC : The following item properties in [HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System] are either missing or have incorrect values in order to disable User Access Control :
[EnableLUA], [ConsentPromptBehaviorAdmin], [LocalAccountTokenFilterPolicy]
At \\dc\share\InfrastructureScripts-206403\VMs\aos1\Configure-PreReqs.ps1:242 char:2
+     Register-UAC -IsUACDisabled:$isUACDisabled -RegPath $regPath -UAC ...
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Register-UAC