Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Win7 loading issue#4463

Merged
daxian-dbw merged 2 commits into
PowerShell:releasePowerShell/PowerShell:releasefrom
adityapatwardhan:Win7LoadingIssueadityapatwardhan/PowerShell:Win7LoadingIssueCopy head branch name to clipboard
Aug 2, 2017
Merged

Win7 loading issue#4463
daxian-dbw merged 2 commits into
PowerShell:releasePowerShell/PowerShell:releasefrom
adityapatwardhan:Win7LoadingIssueadityapatwardhan/PowerShell:Win7LoadingIssueCopy head branch name to clipboard

Conversation

@adityapatwardhan

@adityapatwardhan adityapatwardhan commented Aug 2, 2017 •
edited by iSazonov
Loading

Copy link
Copy Markdown
Member

Since .Net Core 2.0, the api sets were moved to a nuget package. Adding a package reference for "Microsoft.NETCore.Windows.ApiSets" gets the required binaries for the Win7 package.

Opening this PR for release branch. Original PR #4438

Updated by iSazonov:
Fix #3747.

@daxian-dbw daxian-dbw merged commit 0e4f160 into PowerShell:release Aug 2, 2017
@iSazonov iSazonov mentioned this pull request Aug 6, 2017
Closed
@adityapatwardhan adityapatwardhan deleted the Win7LoadingIssue branch August 17, 2017 00:01
2Shirt added a commit to 2Shirt/WizardKit that referenced this pull request Nov 27, 2017
@2Shirt
PowerShell 6 on Win7 failed to build
e7dd6a1 
Start-Process "" -Wait doesn't wait preventing proper extraction of tools.
See these issues:
* PowerShell/PowerShell#2091  (Main issue)
* PowerShell/PowerShell#3747
* PowerShell/PowerShell#4463
@Zetanova

Zetanova commented Apr 11, 2018

Copy link
Copy Markdown

I am still getting the startup error in win7
checked the redist files and the Microsoft.NETCore.Windows.ApiSets packet
both are there.

System.TypeInitializationException: The type initializer for 'System.Management.
Automation.Runspaces.RunspaceFactory' threw an exception. ---> System.DllNotFoun
dException: Unable to load DLL 'api-ms-win-eventing-provider-l1-1-0.dll': The sp
ecified module could not be found. (Exception from HRESULT: 0x8007007E)
at System.Management.Automation.Tracing.EtwActivity.UnsafeNativeMethods.Event
ActivityIdControl(ActivityControlCode controlCode, Guid& activityId)
at System.Management.Automation.Tracing.EtwActivity.GetActivityId()
at System.Management.Automation.Runspaces.RunspaceFactory..cctor()
--- End of inner exception stack trace ---
at System.Management.Automation.Runspaces.RunspaceFactory.CreateRunspace(PSHo
st host, InitialSessionState initialSessionState)

@Zetanova

Zetanova commented Apr 11, 2018

Copy link
Copy Markdown

dotnet is trying to resolve the vcredist dll everywhere beside the nuget package location
C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\Microsoft.NETCore.Windows.ApiSets-x64\1.0.0\runtimes\win7-x64\native

After i added the package runtime.win7-x64.Microsoft.NETCore.Windows.ApiSets explicitly to
the main project, the issue was resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@daxian-dbw daxian-dbw daxian-dbw approved these changes

Assignees

@daxian-dbw daxian-dbw

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@adityapatwardhan @Zetanova @daxian-dbw @msftclas
Morty Proxy This is a proxified and sanitized view of the page, visit original site.