<html>
    <head>
      <base href="https://bugs.documentfoundation.org/">
    </head>
    <body><span class="vcard"><a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> <span class="fn">V Stuart Foote</span></a>
</span> changed
          <a class="bz_bug_link 
          bz_status_NEEDINFO "
   title="NEEDINFO - LibreOffice version 6.3.2.2"
   href="https://bugs.documentfoundation.org/show_bug.cgi?id=127841">bug 127841</a>
          <br>
             <table border="1" cellspacing="0" cellpadding="8">
          <tr>
            <th>What</th>
            <th>Removed</th>
            <th>Added</th>
          </tr>

         <tr>
           <td style="text-align:right;">CC</td>
           <td>
                
           </td>
           <td>mikekaganski@hotmail.com, vstuart.foote@utsa.edu
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_NEEDINFO "
   title="NEEDINFO - LibreOffice version 6.3.2.2"
   href="https://bugs.documentfoundation.org/show_bug.cgi?id=127841#c2">Comment # 2</a>
              on <a class="bz_bug_link 
          bz_status_NEEDINFO "
   title="NEEDINFO - LibreOffice version 6.3.2.2"
   href="https://bugs.documentfoundation.org/show_bug.cgi?id=127841">bug 127841</a>
              from <span class="vcard"><a class="email" href="mailto:vstuart.foote@utsa.edu" title="V Stuart Foote <vstuart.foote@utsa.edu>"> <span class="fn">V Stuart Foote</span></a>
</span></b>
        <pre>A number of potential things could gum up the upgrade install on Windows,
especially is you an instance of soffice.bin running with the QuickStart
feature.

I just now did an upgrade from 6.3.1.2 to 6.3.2.2 with no issues other than the
now common notice to restart because system components needing to be updated
were in use.

None the less the update / restart goes smoothly.

Not to say there is no issue, but we would need a verbose log of your
installation (i.e. run rom a command windows as administrator with msiexec.exe,
and capturing a log with a "/L*v logfileName.txt") to have a look.  You
probably also should have a look in the system event viewer while the install
was running to see if there are any hints of the conflicts there.

=-install-=
Windows 10 Home 64-bit en-US (1903) with
Version: 6.3.2.2 (x64)
Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c
CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; 
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded</pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>