this application could not be started you must enable the net framework что делать
The Update.exe box was tied to the Microsoft Teams icon on the task bar – but I have never installed Microsoft Teams and the updates did not include that application.
Tried to go back to the restore point created just prior to the offending updates (KB4560960 and KB4561600) but after running for 6 hours, it failed saying it couldn’t replace a Firefox file in AppData. Tried many things to resolve the restore problem but nothing worked. Ran chkdsk and sfc which did not find any problems.
I verified that the path referenced in InstallPath existed on my drive. I added all of the entries shown above into my registry. The Release and Version actually reference the November 2019 update but it’s the May 2020 one that is installed and causing trouble. I uninstalled that update again and reinstalled it – it did not make any changes to the registry and the errors continued. The verification tool (netfx_setupverifier.exe), however, now showed versions 2.0, 3.0, 3.5, and every version of 4.x up to 4.7 in the dropdown. Ran this for 4.7 and 4 Full which both failed. The log file said that many files were missing from C:\Windows\Microsoft.NET\Framework64\v4.0.30319 and C:\WINDOWS\Microsoft.NET\assembly. I found another Windows 10 Home computer and compared the files in C:\Windows\Microsoft.NET\Framework64\v4.0.30319 – I have very few files in my folder compared to the «good» computer:
So my registry was missing 4.0 information until I manually added it but many files on the drive are also missing. Everything was fine until the 6/22 update (I also tried uninstalling the updates to no avail, I am limited in which updates I can undo).
Latest version installed.
To add a configuration file, on the Visual Studio menu bar, choose Project, Add New Item. Choose General from the left pane, and then choose Configuration File. Name the configuration file App.config. These menu choices are not available for Windows Store app or Windows phone app projects, because you cannot change the activation policy on those platforms.
Add the element as follows to the application configuration file:
.NET Framework 1.0: «v1.0.3705»
.NET Framework 1.1: «v1.1.4322»
.NET Framework 2.0, 3.0, and 3.5: «v2.0.50727»
.NET Framework 4 and later versions: «v4.0»
| App.config file setting | On computer with version 3.5 installed | On computer with versions 3.5 and 4 or later versions installed | On computer with version 4 or later versions installed |
|---|---|---|---|
| None | Runs on 3.5 | Runs on 3.5 | Displays error message that prompts user to install the correct version* |
| Runs on 3.5 | Runs on 3.5 | Displays error message that prompts user to install the correct version* | |
| Runs on 3.5 | Runs on 3.5 | Runs on 4 or later versions | |
| Runs on 3.5 | Runs on 4 or later versions | Runs on 4 or later versions | |
| Displays error message that prompts user to install the correct version* | Runs on 4 or later versions | Runs on 4 or later versions |
Исполняемый файл не найден
Если исполняемый файл не найден, появляется примерно следующее сообщение.
Имя исполняемого файла определяет то, как вызывается средство. Формат описывается в приведенной ниже таблице.
Глобальные средства
Глобальные средства можно установить в каталоге по умолчанию или в выбранном вами расположении. Каталоги по умолчанию:
| Операционная система | Path |
|---|---|
| Linux/macOS | $HOME/.dotnet/tools |
| Windows | %USERPROFILE%\.dotnet\tools |
Если вы пытаетесь запустить глобальное средство, убедитесь в том, что переменная среды PATH на компьютере содержит путь, по которому установлено глобальное средство, и что исполняемый файл находится по этому пути.
Локальные средства
Среда выполнения не найдена
Накат не выполняется по умолчанию в двух распространенных сценариях:
Если приложению не удается найти подходящую среду выполнения, оно не запускается и сообщает об ошибке.
Помимо предыдущего сообщения, пользователю также выводятся сообщения NuGet, помогающие диагностировать эти сбои. Сообщение NuGet может помочь определить причину проблемы.
Изменение имен пакетов
Корпорация Майкрософт изменила правила в отношении идентификаторов пакетов для средств, из-за чего некоторые средства теперь невозможно найти по прежним именам. Согласно новым правилам имена средств Майкрософт должны иметь префикс «Microsoft.». Этот префикс зарезервирован и может использоваться только для пакетов, подписанных с помощью авторизованного сертификата Майкрософт.
Во время перехода некоторые средства Майкрософт будут иметь старую форму идентификатора пакета, а другие — новую форму:
По мере обновления идентификаторов пакетов необходимо будет перейти на новый идентификатор, чтобы получить последние обновления. Пакеты с упрощенными именами средств станут нерекомендуемыми.
Предварительные выпуски
Веб-канал NuGet недоступен
Неправильный идентификатор пакета
Распространенной причиной ошибок является неправильное имя средства. Такое может случаться из-за ошибок при вводе или из-за того, что средство было перемещено либо устарело. Если средство размещено на сайте NuGet.org, один из способов гарантировать правильность имени — выполнить поиск средства на сайте NuGet.org и скопировать команду установки.
401 (не санкционировано)
Скорее всего, вы указали альтернативный канал NuGet, и этот канал требует проверки подлинности. Вот несколько разных способов решить проблему:
Пример файла конфигурации:
Добавьте необходимые учетные данные в файл конфигурации.
Comments
provegard commented Aug 18, 2020
I have a winexe application which is based on CefSharp.MinimalExample. The project file looks like this:
WinExe netcoreapp3.1 true BrowserWrapper app.manifest false
When I target netcoreapp3.1 and run the resulting exe, I get the following dialog:
I have followed the link to download the lastest 3.1 packages (in particular I though Desktop Runtime 3.1.7 might help, but it didn’t).
These are my SDKs and runtimes:
Am I missing something obvious?
The text was updated successfully, but these errors were encountered:
Dotnet-GitSync-Bot commented Aug 25, 2020
I couldn’t figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.
msftbot bot commented Aug 25, 2020
Tagging subscribers to this area: @vitek-karas, @swaroop-sridhar, @agocke
See info in area-owners.md if you want to be subscribed.
vitek-karas commented Aug 25, 2020
If I change to netcoreapp3.0, I don’t get the dialog.
As for the failure:
provegard commented Aug 31, 2020
@vitek-karas Thank you for your response! I’m building with:
What’s strange is that I cannot reproduce the problem now. I can run the application under 3.1 without the dialog showing. My SDK and runtime lists are the same as they were when I created the issue.
Since I cannot reproduce, I’m closing the issue.
ServerManager.exe – This application could not be started
The Windows Server Manager enables the IT staff to keep a tab on all the servers hosted on a network. The Server Manager tool gives IT staff the ability to manage server roles without having physical access to the servers. If you’re unable to get the Server Manager working, whereby when you click on Server Manager, you encounter the error message ServerManager.exe – This application could not be started, then the solutions presented in this post are intended to help you resolve the issue.
When you encounter this issue, you’ll receive the following full error message;
ServerManager.exe – This application could not be started. L?.
This application could not be started.
Do you want to view Information about this issue?
ServerManager.exe – This application could not be started
Let’s take a look at the description of the process involved concerning each of the listed solutions.
1] Run DISM command
Afterward, the server manager application should open without the error.
2] Manually delete user.config file
3] Edit the ServerList.xml
If you have multiple server OS installations running, you may discover that one of the servers is responsible for the Server Manager error. You can determine this by opening Server Manager on the other servers and try adding servers. All goes well until you try doing the same on a particular server, that’s when the server manager would crash and stop working again. In this case, you can edit the ServerList.xml, and remove the problematic server. The Server Manager should work fine now.
4] Perform System Restore
Similar to the client operating system Windows 10, you can perform a system restore and see if that helps. This is applicable if you are unable to start Server Manager only recently and that things worked fine prior to that.
5] Perform In-place Upgrade Repair
Also, similar to the client OS Windows 10, you can perform an In-place Upgrade Repair and see if that helps.
6] Format and clean install Server OS
As a last resort, you can format and clean install the server OS.
Hope something here helps you.
Date: February 26, 2021 Tags: Errors, Server