Visual Studio 2017 Enterprise: WPF - Operation not supported. Unknown error: 0x80070057

Question

_{Wednesday, July 5, 2017 1:37 AM}

Dear all,

I'm currently developing WPF project.
Unfortunately, when I click on the Debug button, it prompt out the following error:

**Operation not supported. Unknown error: 0x80070057

**

May I know how should I solve this problem?

Thanks for helping hand.

I'm newbie in enterprise as developer.

All replies (7)

_{Wednesday, July 5, 2017 10:11 AM ✅Answered}

Hi Lana,

I already solve the problem.
Solution is the company given me Windows 10 Home and it not match the Visual Studio 2017 Enterprise, after I install the Visual Studio 2017 Community Edition it successfully run.

Thank you.

I'm newbie in enterprise as developer.

_{Wednesday, July 5, 2017 3:09 AM}

Hi friend,

And are you using Entity Framework to get db data?

Could you please show us more info to repro this issue?

Best regards,

Fletcher

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].

_{Wednesday, July 5, 2017 3:30 AM}

Hi Fletch,

I'm not do the anythings with db data.
May I know to to perform the info?

Thank you.

I'm newbie in enterprise as developer.

_{Wednesday, July 5, 2017 5:49 AM}

Hi eng,

Thank you for posting in MSDN forum.

Does this issue occur after creating a new WPF project?

To check if the root cause is pending on the project itself of the VS WPF template, please new a WPF project, debug to see if the same situation happens.

Please try the following steps:

1) Delete this folder: %localappdata%\Microsoft\VisualStudio\15.0_807e9d7b\ComponentModelCache

2) Open Visual Studio and create a new blank WPF project. This will regenerate the deleted folder.

3) Debug the blank project in ripple, first run may complain about a problem with Chrome and the debugger may fail to connect. Close chrome after this, and try debugging one more time and it should connect as desired.

If the any problem persists, please feel free to tell me, we are willing to helping you for more analyze.

Best Regards,

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].

_{Wednesday, July 5, 2017 8:05 AM}

Hi Lana,

This occur when my colleague past the source file to me.

After we get it, we change the path in Debug (Command line arguments) in VS 2017 Visual Studio.

After build and click on debug will get the error above(screenshot).
path: %localappdata%\Microsoft\VisualStudio\15.0_b08a9aae

and I already follow the instruction that you given

also get the same problem again.

Thank you.

I'm newbie in enterprise as developer.

_{Wednesday, July 5, 2017 9:29 AM}

Hi eng,

Thank you for your update.

If the issue still exists on a blank project, there could be an exception on your VS, please re-run the VS 2017 Enterprise installer as administrator, then click the icon besides 'Launch' and choose 'Repair' to perform a repair and launch VS and check if everything is back to normal.

Besides, in order to narrow down some potential environment which could caused this, please check your windows update and make all patches up, clean %temp% folder and run VS as administrator.

Best Regards, 

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].

_{Thursday, July 6, 2017 1:44 AM}

Hi eng,

Thank you for sharing your solution and result here.

Glad to hear you solved this issue successfully, have a good day:)

Best Regards,

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].