<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: HPQTH08.EXE in Operating System - Microsoft</title>
    <link>https://community.hpe.com/t5/operating-system-microsoft/hpqth08-exe/m-p/4071390#M8439</link>
    <description>Log in to the system using a username that has administrator rights. Open a command prompt, then type the command:&lt;BR /&gt;&lt;BR /&gt;CACLS &lt;FULL-PATH-TO-FILE&gt; /E /G BUILTIN\Users:Rwhere &lt;FULL-PATH-TO-FILE&gt; is the full pathname of the runtime file or other component to which the application requires access.&lt;BR /&gt;&lt;BR /&gt;If you don't know the identity of the file that is causing the problem, you could try giving all users read access to all DLL and OCX files in the application folder and the Windows System folder:&lt;BR /&gt;&lt;BR /&gt;CACLS %systemroot%\System32\*.dll /E /G BUILTIN\Users:R&lt;BR /&gt;CACLS %systemroot%\System32\*.ocx /E /G BUILTIN\Users:RThere is really no reason why any user should not have read access to any shared system files.&lt;BR /&gt;&lt;/FULL-PATH-TO-FILE&gt;&lt;/FULL-PATH-TO-FILE&gt;</description>
    <pubDate>Mon, 17 Sep 2007 07:45:30 GMT</pubDate>
    <dc:creator>Jamesbond_2</dc:creator>
    <dc:date>2007-09-17T07:45:30Z</dc:date>
    <item>
      <title>HPQTH08.EXE</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/hpqth08-exe/m-p/4071389#M8438</link>
      <description>&lt;!--!*#--&gt;When I start my computer I get this message:-&lt;BR /&gt;Application failed to initialize properly&lt;BR /&gt;(0X0000135)&lt;BR /&gt;&lt;BR /&gt;Can some one PLEASE explain what this is &amp;amp; can it be removed without interfering with anything else??</description>
      <pubDate>Mon, 17 Sep 2007 04:17:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/hpqth08-exe/m-p/4071389#M8438</guid>
      <dc:creator>baldy_1</dc:creator>
      <dc:date>2007-09-17T04:17:02Z</dc:date>
    </item>
    <item>
      <title>Re: HPQTH08.EXE</title>
      <link>https://community.hpe.com/t5/operating-system-microsoft/hpqth08-exe/m-p/4071390#M8439</link>
      <description>Log in to the system using a username that has administrator rights. Open a command prompt, then type the command:&lt;BR /&gt;&lt;BR /&gt;CACLS &lt;FULL-PATH-TO-FILE&gt; /E /G BUILTIN\Users:Rwhere &lt;FULL-PATH-TO-FILE&gt; is the full pathname of the runtime file or other component to which the application requires access.&lt;BR /&gt;&lt;BR /&gt;If you don't know the identity of the file that is causing the problem, you could try giving all users read access to all DLL and OCX files in the application folder and the Windows System folder:&lt;BR /&gt;&lt;BR /&gt;CACLS %systemroot%\System32\*.dll /E /G BUILTIN\Users:R&lt;BR /&gt;CACLS %systemroot%\System32\*.ocx /E /G BUILTIN\Users:RThere is really no reason why any user should not have read access to any shared system files.&lt;BR /&gt;&lt;/FULL-PATH-TO-FILE&gt;&lt;/FULL-PATH-TO-FILE&gt;</description>
      <pubDate>Mon, 17 Sep 2007 07:45:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-microsoft/hpqth08-exe/m-p/4071390#M8439</guid>
      <dc:creator>Jamesbond_2</dc:creator>
      <dc:date>2007-09-17T07:45:30Z</dc:date>
    </item>
  </channel>
</rss>

