I'm using below command for installing powerShell in VS code tool in a Windows 10 enterprise AVD.
Install-Module Microsoft.Graph -Scope CurrentUser -force
However, getting warning,
WARNING: The version '1.10.0' of module
'Microsoft.Graph.Authntication' is currently in use. Retry the
operation after closing this application.
How it is in use? Is the VS code tool using it for some internal operation? Will it affect the MS Graph functionality?
This type of message is keep on coming for all most all module with version '1.10.0'. I'm unable to get the other versions are getting installed or not. How do I know, when the installation is done? Its really confusing
How to install the latest Graph module perfectly?
Please suggest. Thanks.
thanks for reaching out ,
After the installation is completed, you can verify the installed version with the following command.
Get-InstalledModule Microsoft.Graph
ref doc - https://learn.microsoft.com/en-us/powershell/microsoftgraph/installation?view=graph-powershell-1.0#verify-installation
Hope this helps thanks
please let us know if you have any query.
Related
I have installed PowerShell 7 and installed module PnP.PowerShell, when i tab the commands, it is working [Get-Help of the cmdlet (Get-PnPGroupMember) provides the required output], but when i run the script getting following error not sure.
Failed;https://abc.sharepoint.com/sites/somesite;The 'Get-PnPGroupMember' command was found in the module 'PnP.PowerShell'
Not sure, where and what i am missing ?
After uninstalling Microsoft.Online.SharePoint.PowerShell module and re-installation PnP.PowerShell solved the issue, may the issue is because of having old verision of SharePoint online cmdlets caused the issue.
I just started writing scripts in PowerShell.
The desired script is supposed to create a local GroupPolicyObject (GPO) which will be specified afterwards. Research showed that it could be done with the New-GPO command within the GroupPolicy module for PowerShell. I tried to install the mentioned module but unfortunately nothing I found worked. May I ask for help?
I am using Windows 7 and Powershell 5.1.14409.1005
Error I receive when running example from Microsoft page (New-GPO -Name TestGPO -Comment "This is a test GPO."):
It is actually extremely simple, but the organization of the modules and features has changed many times in the past ten years, Microsoft Docs don't document the up-to-date way anywhere and all articles found online are very old.
Anyway, to install the Powershell Module called GroupPolicy, you need to install the Windows Feature called GPMC (Group Policy Management Console) which includes the mentioned module.
Install-WindowsFeature GPMC
This feature was once a subfeature of the RSAT feature, which is the cause of confusion.
Step 1. Install RSAT from Microsoft site:
https://www.microsoft.com/en-in/download/details.aspx?id=7887
Step 2. Enable Group Policy from Windows Features.
Following link describes the steps in details:
https://www.powershellmagazine.com/2012/05/14/managing-group-policy-with-powershell
Have you installed the RSAT (Remote Server Administration Tools) Group Policy component?
I use WiX 3.7 to write an installer, and I will install a c# system service will try to reinstall the software, using msiexec -x {product_code} -quiet. My OS is Win8
I first install the software through UI, and after a while, the service will create a new process and start to call msiexec, but it failed.
Could you help me on this? I have been struggling for a long time!
Thanks very much!
I have logs as follows:
MSI (s) (7C:80) [00:22:01:708]: Warning: The package code in the cached package 'C:\windows\Installer\134f7d5.msi' does not match the registered package code. Cached
MSI (s) (7C:80) [00:22:01:724]: SOURCEMGMT: Source is invalid due to client source out of sync (product code is the same).
What account is the service and thus the new process running under? Default accounts (e.g. LocalSystem) might not have rights to access the msi information.
That message means that a package is installed with the same ProductCode (set via the Product/#Id attribute) but is not the same package. This usually happens if you install a package, rebuild it (so the new package gets a new "package code") then try to uninstall with the rebuilt package. It can also happen if something is causing source resolution during uninstall and the Windows Installer finds the newly rebuilt package in the place where it expects the old package.
To get unstuck, try re-cache/reinstalling with the newer package then uninstalling:
msiexec /fv path\to\your.msi /l*v install.txt /qb
msiexec /x path\to\your.msi /l*v uninstall.txt /qb
After that, test your scenarios again without changing the MSI in between the updates. You'll slowly be able to track down what is changing in your system that is getting the Windows Installer confused and unhappy.
Good luck!
There is a similar question from stackoverflow. But I didn't find that the answer is helpful. I also used Google searched the websites, I have watched here and here.
I have tried the method they told to solve this problem but not got a satisfied answer.
My operating system is 32-bit Window 7. Noncircle.dll is generated by Matlab version 2010a in another machine which installed Matlab. I tried to add Noncircle.dll as a reference in a project written in C#(I didn't install Matlab on my computer), but Visual-Studio 2010 told me the error:
So I doubt that Noncircle.dll maybe have to be registered. So I put Noncircle.dll in C:\Windows\System32 and started Cmd.exe as a administrator and typed:
regsvr32 Noncircle.dll
Then I got an error:
"The module "Noncircle.dll" failed to load.Make sure the binary is sorted at the
specified path or debug it to check for problems with the binary or depenedent
.DLL files.The specified module coudl not be found."
Could you give me some hints, Thanks in advance!
Updated on 2012/10/18
But if I have installed Matlab version 2010a on my machine, this problem is solved.
I just had the same issue.
If you're running 64-bit Windows and you've placed the 32-bit DLL in Windows\System32\ then it'll give you this error.
Simply place the DLL into Windows\SysWOW64\ and register it from there.
Here's where I found the fix:
http://csi-windows.com/blog/all/73-windows-64-bit/378-fixing-qregsvr32-the-module-failed-to-load-the-specified-module-could-not-be-foundq
First of all try to use RegDllView, to see whether there is actually a COM server registered in the system.
Also check whether this DLL is a COM component.
I know its too late... but I am adding my solution for others because I faced the same error after following above mentioned answers:
"I just had the same issue.
If you're running 64-bit Windows and you've placed the 32-bit DLL in Windows\System32\ then it'll give you this error.
Simply place the DLL into Windows\SysWOW64\ and register it from there."
If you are facing same error after placing DDL to SysWOW64, then you need to turn on MSMQ feature.
Go to Start ->
Search "Turn Windows features on or off" ->
Find "Microsoft Message Queue(MSMQ) Server" and Enable it.
Now, register the same DLL again and this time it will be registered
I'm trying to install NuGet packages like Unity or EntityFramework, but after downloading Nuget cannot install those and returns this error message:
Your machine group policy or user group policy disables execution of PowerShell script.
Adjust your group policy settings to allow execution of PowerShell scripts
How can I resolve this issue? Thanks in advance ;)
Currently old version of NuGet aka not > 1.4 do not sign powershell scripts and thus you need to run the following from a powershell command line:
set-executionpolicy Unrestricted
in 1.4 we are going to sign the scripts so you shouldn't have this problem. Although 1.4 has not shipped yet, but very very soon :)
The above fix might fail if your administrator has locked down powershell scripts in that case you can either ask them to do this for you or wait till NuGet 1.4 is released.