Cannot access windows services

Добрый день уважаемые читатели блога и гости канала, в прошлый раз мы с вами победили ошибку: запуск этого устройства невозможен. (код 10), там у нас были проблемы с установкой оборудования, сегодня же разберем проблему с установкой или удалением программы в десятке. Ситуация такая у вас есть ОС windows 10 или предыдущая редакция, вы пытаетесь установить, например обновление Skype или же удалить какую-то программу с вашего ПК, но в процессе получаете ошибка windows 1719: windows installer service could not be accessed, и в итоге установка или удаление завершается неудачно. Ниже я вам расскажу причину данной проблемы, и мы ее победим на сто процентов.

Что такое Windows installer

Windows installer это специальная служба операционной системы Windows, благодаря которой вы можете устанавливать или удалять приложения в ОС.

Причины ошибки windows 1719

Для начала нужно понять, от чего лечить систему, я вам уже озвучил выше, что windows installer service could not be accessed я получал при установке skype и при удалении программы КриптоПРО, но могу точно вам сказать, что выскочит она везде и при любой попытке инсталляции в Windows 10. Вот как это выглядит.

Еще ошибка 1719 может иметь формулировку Служба установщика Windows недоступна в Windows 10, я такое ловил при установке драйверов рутокен. Нечто похожее мы с вами уже видели, когда Служба установщика Windows недоступна в безопасном режиме

В любом случае проблему устранить нужно, так как мы потеряли возможность, что либо ставить или удалять в Windows 10.

Методы решения ошибки windows 1719

И так давайте разбираться как нам с вами устранить windows installer service could not be accessed. Contact your support personnel to verify that it is property registered and enabled и Служба установщика Windows недоступна в Windows 10.

• Включение службы установщика Windows в ручную > да для начала попробуйте удостовериться, что сервис windows installer включен. Сделать это просто нажимаем клавиши WIN+R и вводим services.msc (другие команды меню выполнить читайте по ссылке).

Находим службу Установщик Winows (Windows Installer), щелкаем по ней правым кликом мыши и выбираем из контекстного меню пункт свойства.

Ее принудительный запуск, в некоторых случаях поможет вам избежать ошибку 1719 в windows 10.

В итоге вы должны получить запущенный сервис, после чего смело закрываем оснастку и пробуем проделать процедуру установки или удаления нужно программы, у меня это КриптоПРО. В моем случае это не помогло, идем дальше.

Если вы внимательный пользователь, то можете обратить внимание, что изменить тип запуска у службы у вас не получиться, это еще идет от времен Windows 8.1, а вот в семерке поменять можно, ради эксперимента выставите в ней автоматический тип запуска и перезагрузитесь, проверьте отсутствие ошибки 1719.

• Итак, если первый метод вам не помог и у вас выскакивает Ошибка 1719. «Не удалось получить доступ к службе установщика Windows», то попробуем произвести процедуру восстановления компонентов системы, для этого откройте командную строку от имени администратора

Если вы получите поврежденные компоненты, то ваша система постарается их восстановить автоматически.

• Если ошибок при сканировании компонентов вы не обнаружили, то проверьте присутствие файла msiexec.exe по путям, описанным ниже, если его там не будет, то вы логично будите постоянно получать: error 1719 windows installer service could not be accessed. Если файла там нет, то скопируйте его с другой системы, либо можете просто переустановить Windows Installer , он спокойно скачивается в интернете.

• Иногда бывают случаи, что сам файл msiexec.exe находится в нужно расположении, но все равно получаете ошибку windows installer service could not be accessed, и причина в том, что библиотека не зарегистрирована. Давайте я покажу как это сделать. Снова запускаете командную строку от имени администратора, это обязательно и делаете вот, что:

Для 32-х битных систем:
msiexec /unregister
msiexec /register

Для 64-х битных систем:
%windir%\system32\msiexec.exe /unregister
%windir%\system32\msiexec.exe /regserver
%windir%\syswow64\msiexec.exe /unregister
%windir%\syswow64\msiexec.exe /regserver

После ручной регистрации сервиса Windows Installer, можете проверять исправилась ли ошибка: error 1719 windows installer service could not be accessed, мне к сожалению, не помогло, но я не расстроился и стал искать дальше.

• Что еще может помочь если вы получаете, что Служба установщика Windows недоступна или windows installer service could not be accessed, как ни странно, при попытке удалить КриптоПРО, он сам может выступать проблемой как для себя, так и для других программ, ломая службу msiexec.exe. Решением, является правка одного ключа реестра, я покажу, что именно нужно исправить и как обычно по традиции выложу ссылку на готовый ключ, чтобы вам было удобно.

Нажимаем WIN+R и вводим regedit, у вас откроется редактор реестра.

Переходим в раздел реестра и исправляем ключ Force с 0 на 1.

После чего перезагружаемся, и о чудо мне это помогло я больше не увидел ни error 1719 windows installer service could not be accessed, ни Служба установщика Windows недоступна, я спокойно смог удалить программу КриптоПРО и больше этой проблемы у меня не возникало, надеюсь вам помогла данная статья и вы смогли устранить очередной глюк Windows 10.

Windows Service cannot access network location (UNC) Path

I have a windows service that polls a folder continuously for new files.For local directories this works fine.But when it comes to UNC Paths on another system in the same network,the service cannot access the folder it seems.I have refereed to this post https://serverfault.com/a/881272 ; it states that i need to run the service as the currently logged in user.How im i supposed to do that?

The path i wish to monitor using the service is

UPDATE:

I have developed the service using topshelf.I want to poll a folder on another local machine in the same network.I go to network places,double click on the computername,it asks for credentials,i enter the username and password of the remote computer i get access to the files on the system for that user(in explorer).

Now when i set the service to run as the local machine user under this machine,it cannot access the remote UNC Path that is accessible using explorer.I have tried installing it as the remote machine user,but it fails.

4 Answers 4

If you try to run your service under the desktop-remote\myname account you probably will fail. The local machine only likes accounts belonging to itself.

What I would do is to turn it around. Make the remote computer share a folder for your machine to poll. That way the remote machine has control over which data it is publishing, just like an object has its properties to private or public . If you are ok with having anyone who knows the address \\desktop-remote\my-not-so-secret-folder\ being able to read it, set it so anyone can read. If you are more secretive, suffix the folder with $ like so: \\desktop-remote\my-secret-folder$ . Now it is not visble but still reachable.
You can also create a special account that has access to said folder.

Then you let your service run any account (with network access) of your choosing on your local machine. Let it try to connect to the remote folder with the special account.

(I have learned, the hard way, that reading a shared folder is slightly different between machines without domain and machines in a domain; the anyone-can-read does not work. At least in WindowsXP it was that way. I have since then not have the need to share a folder.)

Unable to accessing Windows applications from WSL #4793

Comments

kid1412621 commented Jan 2, 2020

Please fill out the below information:

Your Windows build number: Microsoft Windows [Version 10.0.19041.1]

What you’re doing and what’s happening:

follow this document start a node app on Windows (Powershell 7.0.0-rc.1);

request the app from WSL;

• What’s wrong / what should be happening instead:
  Unable access Windows applications from WSL.

The text was updated successfully, but these errors were encountered:

craigloewen-msft commented Jan 2, 2020

Seems likely that this is related to this issue: #4139

therealkenc commented Jan 2, 2020

Seems likely that this is related to this issue: #4139

Related #4619 (it can be both, too).

On the Windows side, listen on 172.17.48.1 (or a subnet) instead of 127.0.0.1 .

numeric-lee commented Jan 20, 2020 •

I was able to use graphic applications in WSL using XMING and Export DISPLAY=:0.0

However, once I upgraded to WSL2 and switching to Export DISPLAY = 172.28.801:0 (my host#) it failed to connect

downloading VcXsrv
switching to another graphics application
running vcxsrv -ac from bash (command not recognized)
running vcxsrv -ac from powershell (command not recognized)
turning firewall off
My Windows 10 build: 19041.1

Here is a typical error message

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-lw’ qt.qpa.screen: QXcbConnection:
Authorization required, but no authorization protocol specified
Could not connect to any X display.

In #4106 you advise to run «vcxsrv -ac» from the bash command line and at least one user accepted that as a solution. I downloaded vcxsrv.exe from sourceforge as an .exe outside of bash, and I see no way to execute it from bash

fredericseiler commented Jan 22, 2020

A quick & dirty workaround

Install VcXsrv, then run XLaunch:

Specify your display port:

Select «Start no client»:

Don’t forget to check «Disable access control» (the «-ac» switch, listen on all interfaces):

Finish the configuration and verify that VcXsrv is actually listening on all interfaces ( hostname:0.0 ):

Find your host LAN IP address (your real Ethernet/Wifi IP, ex. 192.168.1.3)

On your wsl distro shell, modify the $DISPLAY env:

Then, you can start any GUI app:

At the time of writing, for any wsl > host connection, you have to listen on the host side for all interfaces (eg. 0.0.0.0) and specify the host LAN IP address on the wsl distro side:

If you really want to use the /etc/resolv.conf host IP address (the one from the Hyper-V virtual ethernet adapter), you have to play with the public profile of Windows Defender Firewall. At your own risk. Dealing with private profile rules makes me much more comfortable.

numeric-lee commented Jan 29, 2020 •

@fredericseiler @therealkenc
Thanks for the clear response and the additional details
I followed your instructions, still experiencing the same issues
I am running with the windows firewall turned off
the IP address has been dummified

(base) yy@ZZ: $ export DISPLAY=999.88.77.1:0.0
(base) yy@ZZ: $ export LIBGL_ALWAYS_INDIRECT=1

example 1

(base) yy@ZZ: $ spyder &
[1] 18558
(base) yy@ZZ: $ QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to ‘/tmp/runtime-yy’
qt.qpa.screen: QXcbConnection: Could not connect to display 999.88.77.1:0.0
Could not connect to any X display.

example 2

(base) yy@ZZ: $ glxgears &
[1] 19820
(base) yy@ZZ: $ Error: couldn’t open display 999.88.77.1:0.0

Any additional suggestions? any workarounds where I fallback on the methods which worked successfully in WSL1?

fredericseiler commented Jan 29, 2020

It’s one of a kind IP address you got there.

numeric-lee commented Jan 29, 2020

The iP address has been dummified 🙂

fredericseiler commented Jan 29, 2020

Didn’t see that part, my bad. You don’t need to obfuscate the IP, as only devices in your own private network can reach it. Or maybe are your trying to use your WAN IP ?

What is the result of a ping host_lan_ip_address from your WSL distro ?

numeric-lee commented Jan 29, 2020

@fredericseiler @therealkenc
I just solved it with that last hint. Your instructions were accurate, superior to the official documentation, and much appreciated. However, there were two different IPv4 Addresses, one for the Ethernet adapter and one for the WiFI. Once I substituted the second IPV4 address, it worked. Thanks so much.

fredericseiler commented Jan 29, 2020

I’m glad if that helped you 😉

Alternatively, you can mess around with the Windows Firewall and disable the WSL interface protection (while letting the Firewall turned on for the other interfaces) every time you start your computer (for example, via a powershell script in a scheduled task). This way, you can use the host Hyper-V IP (the one from /etc/resolv.conf ). And as a bonus, you can add linux-side services automatic startup in your script.

• Wait for the public 20H1 release, hoping that the clever guys of MS figured out something to fix this issue (and others)
• Linux in a VM (awfully slow and unsuitable for coding and keyboard shortcuts)
• The full Linux desktop experience (my laptop is unfortunately not a ThinkPad, so it was just shitty for me; Nvidia Optimus issues, no battery charging limit, and so on)
• Buy an overexpensive Mac like every other dev who just ship things instead of bothering with this like us.

winest commented Feb 19, 2020 •

I come up with an script after checking discussions, which makes things easier without adding Firewall rules and not exposing public IP.

[Updated Feb.21]
For enterprise firewall, try also adding this
powershell -Command «Set-NetFirewallProfile -DisabledInterfaceAliases \»vEthernet (WSL)\»»

To make it works:

1. On Windows, save the following code as xxx.bat, and you can make it run when boot if you like:

1. In WSL, edit

   /.bashrc file to add following lines:

That’s all to make WSL2 works automatically. The idea is to get the private LAN IP of WSL interface on Windows, and use Environment variable to pass to WSL. WSL then update this LAN IP to DISPLAY for X-Server connection.

gx761 commented Feb 27, 2020

This issue should not be closed, the solution provided by @fredericseiler only works when the service on host machine is listening on 0.0.0.0. But in my case, there is a proxy service listening on localhost, and the service is initiated by another software which is not configurable. To access any internal resources from my company, I have to visit through this proxy. Before, in wsl1, the proxy is usable by setting —proxy=http://127.0.0.1:12639. However, since wsl2 does not have built-in support for this and the solution mentioned above cannot deal with this either, I really hope the microsoft team can put some serious effort on this and give us a clean solution. Just try to be consistent with the wsl1.

KindDragon commented Mar 19, 2020

nyc-tinker commented Mar 22, 2020 •

I have two different devices with win 10 pro, one where wsl2 can connect to a 127.0.0.1 app (thinkpad t480), but the other laptop (an older Celeron Acer) is unable to do so with the same configuration. Both are win 10 pro, «slow» insider build (# 19041).

Getting «connection refused» errors on wsl2 Debian using curl to test, after having set up nodejs on the windows side and running node on the test app app.js. This app is listening on http://127.0.0.1:3000. cmd.exe on the windows side connects successfully using curl to 127.0.0.1:3000, so can confirm it’s up.

Firewall settings allow node.exe allowed on private and public networks. Racking my head and can’t figure it out, esp since the other laptop has the same config and just works!

The fact I don’t have to explicitly specify IP address of the windows host on the thinkpad suggests you don’t have to in all cases?

gwd999 commented Mar 29, 2020 •

same problem — none of the above work on WSL2 neither with Xming nor with VcxSrvr. Tried all of them EXPORT DISPLAY=localhost:0.0 (or 127.0.0.1) or DISPLAY=Some.WSL.IP.Address:0 -> NOPE nothing can be done to make WSL2 (in my case Ubuntu 18.04) run some xeyes or xclock X-Windows, not to mention any Firefox or similar app. The only solution for me was to set up a fully fledged X-Windows env on Ubuntu and log into it via Remote Desktop; NOT really what was intended with WSL2 in the first place, was it?

fquinner commented Apr 1, 2020

For what it’s worth, I put some documentation together on how to get the firewall playing nicely with X11 here:

My main problem was I didn’t realize that that security prompt actually adds a Block rule when you uncheck that box as opposed to simply deciding not to add an Allow rule. So I needed to both disable that rule, and add my own to allow the path through.

The IP i use in my .bashrc is from:

famelis commented Apr 5, 2020 •

(2nd update)
I created some scripts, which can be run either when boot or from WSL or from Powershell.

They launch, in a transparent manner. a windowed KDE, using VcXsrv and the accompanying Xlaunch. It works very well and has no problems with reboots or shutting it down and back again