Sandboxie-Plus 1.16.1 (Pre-release)

Discussion in 'Sandboxie (SBIE Open Source) Plus & Classic' started by DavidXanatos, Jul 6, 2025.

  1. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    2,560
    Location:
    Viena
    I have identified the issue, connecting to the windows task scheduler service blocks for about a minute when the required RPC port is not available.
    If you wait long enough FF will work normally.
    there is a workaround
    ClosedClsid={0F87369F-A4E5-4CFC-BD3E-73E6154572DD}
    I'm looking further into that issue for a better fix, or to confirm that this one is good enough
     
  2. Brummelchen

    Brummelchen Registered Member

    Joined:
    Jan 3, 2009
    Posts:
    6,332
    the schedule service?
     
  3. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    2,560
    Location:
    Viena
  4. Brummelchen

    Brummelchen Registered Member

    Joined:
    Jan 3, 2009
    Posts:
    6,332
    !
     
  5. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    2,560
    Location:
    Viena
    ?
     
  6. Brummelchen

    Brummelchen Registered Member

    Joined:
    Jan 3, 2009
    Posts:
    6,332
    the UUID you gave is from the "task scheduler", thats right. and its a service. sorry, for the interruption.
    but i dont see any connection to RPC. (to the remote)
     
  7. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    2,560
    Location:
    Viena
    taskschd.dll uses RPC to communicate with the service and offer an API to enum/add/remove/alter scheduler Tasks.
    Instantiating this interface since that KB hands for about 60 second, by entirely blocking that interface we avoid the wait and fail fast.
     
  8. catspyjamas

    catspyjamas Registered Member

    Joined:
    Jul 1, 2011
    Posts:
    300
    Location:
    New Zealand
    @DavidXanatos to answer your question on the previous page, the problem is present on ANY version of FF, not just 140 & 141, it's also present on 136.4 (as far back as I have tried). The problem began with updating to the preview CU KB5062660 that takes Windows to 24H2 build 26100.4770. Uninstalling this Windows update resolves the issue, for any version of firefox. The workaround on the other page to paste: OpenIpcPath=firefox.exe,\RPC Control\epmapper into the relevant sandbox ini fixes the problem on all the laptops in the house.

    BTW I have found that waiting to let it resolve as per your above comment has not worked on our machines. It was still not working after leaving it for 30mins on the machine I gave it that long with.... BTW I'm not using the portable version of FF like the person on github.

    EDIT: Just tried your workaround: ClosedClsid={0F87369F-A4E5-4CFC-BD3E-73E6154572DD} & that works on the machine I tried it on running 24H2 build 26100.4770. Deleted the line OpenIpcPath=firefox.exe,\RPC Control\epmapper before testing, obviously. Thanks!
     
    Last edited: Jul 28, 2025 at 1:41 AM
  9. DavidXanatos

    DavidXanatos Developer

    Joined:
    Sep 6, 2006
    Posts:
    2,560
    Location:
    Viena
    Yes the issue is not FF specific a short test code from Chatty to Enum all scheduled tasks suffers from the same freeze behavior.
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.