Portmaster Core Service is not starting when I click on 'START CORE SERVICE'.

[FlawlessCasual17]

Pre-Submit Checklist:

• Check applicable sources for existing issues:
  • Windows Known Issues
  • Linux Known Issues
  • Github Issues

What happened: Portmaster Core Service is not starting when I click on 'START CORE SERVICE'.

What did you expect to happen?: Portmaster should start normally when I click on 'START CORE SERVICE'. I have been using Portmaster for 5 months now, I had no issues with it until today.

How did you reproduce it?: The video here shows how I reproduced it: https://youtu.be/bYFnh870Q4E

Debug Information:

logs.zip

[dhaavi]

Hey @KrisSchneider, thanks for reporting this.

It looks like there is a problem with the app gaining the required permission to start the core service:

Error occurred in handler for 'api.startService': {
  error: Error: User did not grant permission.
      at C:\ProgramData\Safing\Portmaster\updates\windows_amd64\app\portmaster-app_v0-2-3\resources\app.asar\node_modules\sudo-prompt\index.js:534:29
      at ChildProcess.exithandler (node:child_process:413:5)
      at ChildProcess.emit (node:events:394:28)
      at maybeClose (node:internal/child_process:1064:16)
      at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5),
  stdout: '',
  stderr: ''
}

When did this happen? Did you just boot or did you previously shut down Portmaster? Does a reboot start the core service correctly? Can you start the core service manually from the Windows service manager?

The logs you provided did not contain any logs from the core service.

[FlawlessCasual17]

When did this happen?

It happened today at 8:30 am (MST).

Did you just boot or did you previously shut down Portmaster?

I just booted Portmaster, after reinstalling it. I previously uninstalled Portmaster, restarted my computer. Then, I reinstalled it using the installer provided on your website (safing.io).

Does a reboot start the core service correctly?

No, it does not. I would have to click on tray icon and have to do it manually. Although, do to an error, I cannot do that right now.

The logs you provided did not contain any logs from the core service.

The logs I provided were wrong? Do you want me to reinstall Portmaster again to provide you with different logs? I currently don't have it on my system, as I uninstalled it 2 hours ago. I don't mind reinstalling it again.

[FlawlessCasual17]

Also, could you show what was wrong with the log files I provided earlier?

[dhaavi]

I just booted Portmaster, after reinstalling it. I previously uninstalled Portmaster, restarted my computer. Then, I reinstalled it using the installer provided on your website (safing.io).

Ok. Did you reinstall it because something did not work? Did you let the uninstaller also delete the data during uninstalling?

No, it does not. I would have to click on tray icon and have to do it manually. Although, do to an error, I cannot do that right now.

Can you try running the Portmaster directly? Open a cmd with admin privileges and run:

C:\ProgramData\Safing\Portmaster\portmaster-start.exe core --data C:\ProgramData\Safing\Portmaster

The logs I provided were wrong?

I was not sure. If you haven't excluded the logs from the core, then I guess it just never started, which seems plausible with your provided information.

[FlawlessCasual17]

I'm sorry if I'm not able to reply in a while. I'm currently in a business meeting which could take a lot of time. Furthermore, I might be able to reply after 1 hour and 30 mins from now.

[FlawlessCasual17]

Ok. Did you reinstall it because something did not work?

Yes, thats why I did that.

Did you let the uninstaller also delete the data during uninstalling?

Yes.

Can you try running the Portmaster directly? Open a cmd with admin privileges and run: C:\ProgramData\Safing\Portmaster\portmaster-start.exe core --data C:\ProgramData\Safing\Portmaster

I am currently running this command right now through powershell, I am getting a lot of crazy output like this:

220601 18:56:22.003 connection:639 > INFO 183 filter: connection MSI\krist:C:\Users\krist\scoop\apps\brave\1.39.111\brave.exe:11500 to dns.quad9.net. (2620:fe::fe) blocked: bypass prevention: blocked rogue connection to DNS resolver
220601 18:56:22.080 pat/notify:170 > WARN 184 compat: detected secure dns bypass issue with C:\Users\krist\scoop\apps\brave\1.39.111\brave.exe
220601 18:56:22.080 connection:639 > INFO 186 filter: connection MSI\krist:C:\Users\krist\scoop\apps\brave\1.39.111\brave.exe:11500 to dns.quad9.net. (2620:fe::fe) blocked: bypass prevention: blocked rogue connection to DNS resolver
220601 18:56:22.206 pat/notify:170 > WARN 187 compat: detected secure dns bypass issue with C:\Users\krist\scoop\apps\brave\1.39.111\brave.exe
220601 18:56:22.206 connection:639 > INFO 189 filter: connection MSI\krist:C:\Users\krist\scoop\apps\brave\1.39.111\brave.exe:11500 to dns.quad9.net. (149.112.112.112) blocked: bypass prevention: blocked rogue connection to DNS resolver
220601 18:56:22.298 pat/notify:170 > WARN 190 compat: detected secure dns bypass issue with C:\Users\krist\scoop\apps\brave\1.39.111\brave.exe
220601 18:56:22.298 connection:639 > INFO 192 filter: connection MSI\krist:C:\Users\krist\scoop\apps\brave\1.39.111\brave.exe:11500 to dns.quad9.net. (149.112.112.112) blocked: bypass prevention: blocked rogue connection to DNS resolver
220601 18:56:22.378 pat/notify:170 > WARN 193 compat: detected secure dns bypass issue with C:\Users\krist\scoop\apps\brave\1.39.111\brave.exe
220601 18:56:22.378 connection:639 > INFO 195 filter: connection MSI\krist:C:\Users\krist\scoop\apps\brave\1.39.111\brave.exe:11500 to dns.quad9.net. (149.112.112.112) blocked: bypass prevention: blocked rogue connection to DNS resolver
220601 18:56:23.117 connection:639 > INFO 196 filter: connection MSI\krist:C:\Users\krist\scoop\apps\thunderbird\91.10.0\thunderbird.exe:9864 -> 2603:1036:102:7a::2 accepted: allowed by default action
220601 18:56:24.197 pat/notify:170 > WARN 197 compat: detected secure dns bypass issue with C:\Users\krist\scoop\apps\brave\1.39.111\brave.exe
220601 18:56:24.197 connection:639 > INFO 199 filter: connection MSI\krist:C:\Users\krist\scoop\apps\brave\1.39.111\brave.exe:11500 to dns.quad9.net. (2620:fe::9) blocked: bypass prevention: blocked rogue connection to DNS resolver
220601 18:56:24.197 pat/notify:170 > WARN 200 compat: detected secure dns bypass issue with C:\Users\krist\scoop\apps\brave\1.39.111\brave.exe
220601 18:56:24.197 connection:639 > INFO 202 filter: connection MSI\krist:C:\Users\krist\scoop\apps\brave\1.39.111\brave.exe:11500 to dns.quad9.net. (2620:fe::9) blocked: bypass prevention: blocked rogue connection to DNS resolver
220601 18:56:24.506 pat/notify:170 > WARN 203 compat: detected secure dns bypass issue with C:\Users\krist\scoop\apps\brave\1.39.111\brave.exe
220601 18:56:24.506 connection:639 > INFO 205 filter: connection MSI\krist:C:\Users\krist\scoop\apps\brave\1.39.111\brave.exe:11500 to dns.quad9.net. (9.9.9.9) blocked: bypass prevention: blocked rogue connection to DNS resolver
220601 18:56:24.506 pat/notify:170 > WARN 206 compat: detected secure dns bypass issue with C:\Users\krist\scoop\apps\brave\1.39.111\brave.exe
220601 18:56:24.506 connection:639 > INFO 208 filter: connection MSI\krist:C:\Users\krist\scoop\apps\brave\1.39.111\brave.exe:11500 to dns.quad9.net. (9.9.9.9) blocked: bypass prevention: blocked rogue connection to DNS resolver
220601 18:56:29.230 pat/notify:170 > WARN 209 compat: detected secure dns bypass issue with C:\Users\krist\scoop\apps\brave\1.39.111\brave.exe
220601 18:56:29.230 connection:639 > INFO 211 filter: connection MSI\krist:C:\Users\krist\scoop\apps\brave\1.39.111\brave.exe:11500 to dns.quad9.net. (2620:fe::9) blocked: bypass prevention: blocked rogue connection to DNS resolver
220601 18:56:29.537 pat/notify:170 > WARN 212 compat: detected secure dns bypass issue with C:\Users\krist\scoop\apps\brave\1.39.111\brave.exe
220601 18:56:29.537 connection:639 > INFO 214 filter: connection MSI\krist:C:\Users\krist\scoop\apps\brave\1.39.111\brave.exe:11500 to dns.quad9.net. (9.9.9.9) blocked: bypass prevention: blocked rogue connection to DNS resolver

[FlawlessCasual17]

I hope I don't have to run Portmaster like this in the future. I prefer the GUI more than this terminal.

[FlawlessCasual17]

Here is my portmaster folder, if you need more information. Kris's Portmaster folder.zip

[FlawlessCasual17]

Hello, is this issue solved or I am still on wait?

[dhaavi]

Hey @KrisSchneider, thanks for the additional data, I will look further into this. We have many open issues and cannot assign sufficient resources as to work on every issues daily. It might take a while, but we will continue to work on all issues.

[FlawlessCasual17]

Okay, I will wait then. Thank you @dhaavi for updating me on the current situation.

[dhaavi]

Here is my portmaster folder, if you need more information. Kris's Portmaster folder.zip

Thanks! I tried to download, but it always stops at 68.94% for some reason. Did you zip the whole folder? Please just share the logs dir - it's enough. Also, please always delete the files after we got them, they can contain sensitive data.

Can you try to start the service from the Windows Service Manager and then send me log files from that one? Then I can look into why it won't start then run by Windows.

[FlawlessCasual17]

@dhaavi were you able to successfully download the file?

[FlawlessCasual17]

Also, I have nothing valuable on this laptop. Everything else is backed up on another computer.

[MMZThumper]

I've been having this same issue but it was after installing it for the very first time. I contacted support via email and they suggested I give this post a read. I haven't tried running it from the Cmd line but I will give it a try probably tomorrow. I hope nobody minds me jumping into this thread!

[FlawlessCasual17]

I don't mind anyone jumping in this thread, just please keep it civil. Thats all.

[MMZThumper]

Most definitely! 👍🏻

[MMZThumper]

Alright. So, I was finally able to reinstall Portmaster and just like before, the app installed fine without any errors. I restarted and at first The Notifier was red but now it's turned green. There was no desktop icon created during installation, so I had to search for it. I R-clicked on it and ran as admin. A few seconds later I received this Java error. After I closed it, the same screen popped up as before stating that Portmaster's Core Service wasn't running and when I click on "Start" nothing happens. I tried running the Cmd's that were suggested but that just resulted in some process starting and stopping repeatedly until I closed PowerShell. I'll attach screenshots of both errors if I can. I've tried all solutions posted in this thread and have no idea what I should do next. I don't want to create another problem report when the author of this post is experiencing the exact same issue I am. So, I thought it would be best that I join in here. Below is the info about Windows running on my laptop. If there is any other information you need, or if it is preferred that I create my own thread, please let me know.

Edition Windows 11 Home Version 22H2 Installed on ‎5/‎17/‎2022 OS build 22621.1 Experience Windows Feature Experience Pack 1000.22632.1000.0

[FlawlessCasual17]

This issue is also happening on Windows 11? Wow. Also, sorry for not being able to reply for a few weeks. I have been focusing on college work for most of my time.

[MMZThumper]

Yes, it is. It happened the very first time I installed the software!

[dhaavi]

@dhaavi were you able to successfully download the file?

Sadly, no. Were you able to upload it again?

I restarted and at first The Notifier was red but now it's turned green.

If the notifier turns green, then everything should be in order.

I R-clicked on it and ran as admin.

Running things as admin is not necessary for Portmaster (this was just the UI), and is also generally discouraged. The only thing needing admin privileges is the system service, which gets them anyway.

A few seconds later I received this Java[script] error.

This seems to an internal error of the UI. Interesting - also that it was gone on next start.

After I closed it, the same screen popped up as before stating that Portmaster's Core Service wasn't running and when I click on "Start" nothing happens.

This hints at the Portmaster system service not having started correctly.

Looking at the output you posted I am not sure if this is the same problem - but it produces the same effect. I'd leave both issues in here for now and let's see where we go from here.

Can you share the full log file from the core service? You can find the log files in C:\ProgramData\Safing\Portmaster\logs\core. I'd recommend you upload it to a pastebin with a time or send us an email with it - if you do, please notify me here about it.

[FlawlessCasual17]

Hello, what's happening, any new updates to this issue?

[dhaavi]

Hey @KrisSchneider, I think you might have missed my comment posted just right before yours: https://github.com/safing/portmaster/issues/673#issuecomment-1161508921

[FlawlessCasual17]

Here you go @dhaavi, I uploaded the file to a different cloud storage this time. https://mega.nz/file/nGJTASqS#d73Um6YsuNPlbxYr2ezrs1aH0a4qOsrLSve9hhVIxR8

[FlawlessCasual17]

Sorry for waiting. If the link does not work, please tell me right away. I will get back to you right away.

[dhaavi]

Hey @KrisSchneider,

I just wanted to download, but it said:

The file you are trying to download is no longer available This could be due to the following reasons: The file has been removed as it violated our Terms of Service. Invalid URL - the link you are trying to access does not exist. The file has been deleted by the user.

[FlawlessCasual17]

@dhaavi sorry I forgot that I was sharing something with you, here you go I reuploaded it to my drive. https://mega.nz/file/nWJB0LKR#wOHm_beXsYCsrMLFMIZ9SzSFBeLuy6TfRTX3G-eSzes

[dhaavi]

Thanks for the tip from @aaronsvk in #498.

He found out that it was the disabled Windows Event Log system that was the problem for him.

I found the same in @KrisSchneider's logs (please delete them now):

failed to open eventlog: The RPC server is unavailable.

Can everyone here check if they have the Windows Event Log service enabled and running?

You can also test if this is the problem by executing:

C:\ProgramData\Safing\Portmaster\portmaster-start.exe core-service --data C:\ProgramData\Safing\Portmaster

This is the same as running Portmaster from the cmd, but it registers with the Windows Service Manager, and also logs to Windows Event Log - which seems to be the problem.

I will investigate if we can disable or ignore a missing Windows Event Log.

---

I also have a new idea about the issue with the javascript error about insufficient permissions:

It could be that an anti-virus system won't let you elevate privileges, leading the Portmaster UI to not even asking you about permissions, but failing directly.

[FlawlessCasual17]

Windows Event Log is running and enabled on my device:

[dhaavi]

@KrisSchneider: Interesting, can you try running: C:\ProgramData\Safing\Portmaster\portmaster-start.exe core-service --data C:\ProgramData\Safing\Portmaster