File: vboxsvc-session-0-known-issues.dita

package info (click to toggle)
virtualbox 7.1.12-dfsg-2
  • links: PTS, VCS
  • area: contrib
  • in suites: sid
  • size: 565,672 kB
  • sloc: ansic: 2,330,854; cpp: 2,193,228; asm: 230,777; python: 223,895; xml: 86,771; sh: 25,541; makefile: 8,158; perl: 5,697; java: 5,337; cs: 4,872; pascal: 1,782; javascript: 1,692; objc: 1,131; lex: 931; php: 906; sed: 899; yacc: 707
file content (18 lines) | stat: -rw-r--r-- 760 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
<topic xml:lang="en-us" id="vboxsvc-session-0-known-issues">
  <title>Known Issues</title>
  
  <body>
    <ul>
      <li>
        <p>Due to different Windows sessions having their own set of resources, there might be some issues with
          accessing network shares created in the interactive user session when at least one of the <ph
            conkeyref="vbox-conkeyref-phrases/product-name"/> processes are running in session 0. </p>
        <p>For accessing network shares within session 0, a possible workaround is to establish permanent access to the
          share and then restart the host. </p>
      </li>
    </ul>
  </body>
  
</topic>