-
Notifications
You must be signed in to change notification settings - Fork 338
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some Apps did not install due to an internal error #1562
Comments
Can you reproduce the errors and share log files? |
/logs |
Hi @KarlSheldon. It would be helpful for us if you could share your Dev Home logs. These logs can be found at |
Dont know if its the same error Just followed this steps
|
Hi Sorry for the late reply, hope these help, I could not get several to
install so I installed separately and all went OK,I have since ran
devhome and it allowed some installs over existing,
Thanks
*--*--*--*--*--*--*--*--*--*--*--*---*--*--*--*--*--*--*--
email: ***@***.***
*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--
…On Tue, 19 Sept 2023 at 18:46, microsoft-github-policy-service[bot] < ***@***.***> wrote:
Hi @KarlSheldon <https://github.com/KarlSheldon>. It would be helpful for
us if you could share your Dev Home logs. These logs can be found at
%LOCALAPPDATA%\Packages\Microsoft.Windows.DevHome_8wekyb3d8bbwe\TempState
and
%LOCALAPPDATA%\Packages\Microsoft.Windows.DevHomeGitHubExtension_8wekyb3d8bbwe\TempState.
You can share these folders via a OneDrive link or zip them and attach them
to a comment here. If you share this way, you may want to look through the
logs in case there are any details included that you would like to remove
(for example, private repo names). Alternatively, you can open a Feedback
Hub issue and attach them there. If you use Feedback Hub, please paste the
URL at the bottom of the report here so we can easily find it.
—
Reply to this email directly, view it on GitHub
<#1562 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATQWNVTZCOR2CSP3I6ACPPTX3HK7BANCNFSM6AAAAAA43C46SI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@KarlSheldon, sorry for the delayed response. I've recently refactored WinGet's integration in the PRs below. Would it possible to validate if the issue still repros in latest Dev Home version?
|
I am happy to report that I have now used devhome to install on 4 machines
without issues. Tried to trip it up with some apps already installed but it
now works as intended,
Thanks
…On Sat, 6 Jul 2024, 03:21 AmirMS, ***@***.***> wrote:
@KarlSheldon <https://github.com/KarlSheldon>, sorry for the delayed
response. I've recently refactored WinGet's integration in the PRs below.
Would it possible to validate if the issue still repros in latest Dev Home
version?
- #2089 <#2089>
- Added recovery when RPC exceptions occur.
- #3134 <#3134>
- Elevated process now uses the same WinGet logic as Dev Home's
main process (enhanced implementation overall + recovery)
- #3307 <#3307>
- Mitigated an issue that occurs when Dev Home's elevated process
attempts to install multiple packages at the same time.
—
Reply to this email directly, view it on GitHub
<#1562 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATQWNVRLWPYBMKLHWPQGWUDZK5ICVAVCNFSM6AAAAAA43C46SKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJRGU4TAOBTGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Dev Home version
0.401.226.0
Windows build number
10.0.22631.2338
Other software
OS Build Version: 10.0.22631.2338.amd64fre.ni_release.220506-1250
.NET Version: .NET 6.0.20
Steps to reproduce the bug
Installing all apps
Expected result
All to install without issue
Actual result
Docker, Intelj and Unity did not install
Included System Information
Physical Memory: 63.92GB (51.01GB free)
Processor Architecture: x64
Included Extensions Information
Extensions:
Microsoft.Windows.DevHome_0.401.226.0_x64__8wekyb3d8bbwe
Microsoft.Windows.DevHomeGitHubExtension_0.400.226.0_x64__8wekyb3d8bbwe
The text was updated successfully, but these errors were encountered: