Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Visual Studio Build Errors #59775

Open
vsfeedback opened this issue Jan 8, 2025 · 3 comments
Open

Visual Studio Build Errors #59775

vsfeedback opened this issue Jan 8, 2025 · 3 comments
Labels
Author: Migration Bot 🤖 The issue was created by a issue mover bot. The author may not be the actual author. needs-area-label Used by the dotnet-issue-labeler to label those issues which couldn't be triaged automatically

Comments

@vsfeedback
Copy link

This issue has been moved from a ticket on Developer Community.

[severity:I'm unable to use this version]
Unable to resolve. Have reinstalled and reset VS 2022. Have reset and reinstalled OS then a fresh install of VS 2022. Still receiving same error message (screenshot below).

VS Build Error.png

Any help would be greatly appreciated as I a unable to develop applications for customers.

Original Comments

Feedback Bot on 1/7/2025, 08:59 PM:

We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label Used by the dotnet-issue-labeler to label those issues which couldn't be triaged automatically label Jan 8, 2025
@dotnet-policy-service dotnet-policy-service bot added the Author: Migration Bot 🤖 The issue was created by a issue mover bot. The author may not be the actual author. label Jan 8, 2025
@MackinnonBuck
Copy link
Member

@javiercn, does this look like a dupe of one of the issues you've been investigating?

@AdamBauerle
Copy link

I can add to this that the issue appears to follow my user (I've tried both a personal MS account and a work MS account).

@AdamBauerle
Copy link

I have also tried it without a MS account and that is the only way I could get VS to work without issue. As soon as I use VS on a Windows signed in MS account (personal or work), it does not work. Tried this on several machines, different Windows 11 installs (both 23H2 and 24H2 installs). Does not seem to matter if it is a new install or an already existing install of Windows 11.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Author: Migration Bot 🤖 The issue was created by a issue mover bot. The author may not be the actual author. needs-area-label Used by the dotnet-issue-labeler to label those issues which couldn't be triaged automatically
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@MackinnonBuck @vsfeedback @AdamBauerle