<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="de">
	<id>https://wiki.heidler-strichcode.de/w/index.php?action=history&amp;feed=atom&amp;title=HVS32_crash_under_Windows_10</id>
	<title>HVS32 crash under Windows 10 - Versionsgeschichte</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.heidler-strichcode.de/w/index.php?action=history&amp;feed=atom&amp;title=HVS32_crash_under_Windows_10"/>
	<link rel="alternate" type="text/html" href="https://wiki.heidler-strichcode.de/w/index.php?title=HVS32_crash_under_Windows_10&amp;action=history"/>
	<updated>2026-08-09T15:33:14Z</updated>
	<subtitle>Versionsgeschichte dieser Seite in Wiki - Heidler Strichcode GmbH</subtitle>
	<generator>MediaWiki 1.35.2</generator>
	<entry>
		<id>https://wiki.heidler-strichcode.de/w/index.php?title=HVS32_crash_under_Windows_10&amp;diff=5848&amp;oldid=prev</id>
		<title>Lappl: Translate</title>
		<link rel="alternate" type="text/html" href="https://wiki.heidler-strichcode.de/w/index.php?title=HVS32_crash_under_Windows_10&amp;diff=5848&amp;oldid=prev"/>
		<updated>2024-07-05T09:16:11Z</updated>

		<summary type="html">&lt;p&gt;Translate&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Neue Seite&lt;/b&gt;&lt;/p&gt;&lt;div&gt;[[de:HVS32_absturz_unter_Windows_10]]&lt;br /&gt;
&lt;br /&gt;
= Problem =&lt;br /&gt;
&lt;br /&gt;
The HVS32 link refers to a connected network drive ( e.g.: V:\HVS32 ... ). Under Windows 10, the connection to this drive may be briefly interrupted, causing HVS32 to crash.[[File:UNC-Pfad.PNG|frameless|right|400px|UNC-Pfad.PNG]]&lt;br /&gt;
&lt;br /&gt;
The reason for the network drive disconnection in Windows 10 is the changed behavior for updating group policies, which leads to the network drives being disconnected for a short time during these updates, causing applications that are started from network drives to crash accordingly.&lt;br /&gt;
&lt;br /&gt;
&amp;amp;nbsp;&lt;br /&gt;
&lt;br /&gt;
= Solution =&lt;br /&gt;
&lt;br /&gt;
As of version [[HVS32_Update_ENG|7.102.13]], the HVS32 can be linked via UNC path (e.g. \\server\hvs32...), which means that a connected network drive is no longer required.&lt;br /&gt;
&lt;br /&gt;
Right-click on the HVS32 shortcut -&amp;gt; Properties -&amp;gt; &amp;quot;Shortcut&amp;quot; tab&lt;br /&gt;
&lt;br /&gt;
-&amp;gt; Change the entry in the &amp;quot;Target:&amp;quot; line to the UNC path of the HVS32 and select the HVS32.exe (e.g.: \\server\hvs32\HVS32.exe )&amp;lt;br/&amp;gt; -&amp;gt; Change the &amp;quot;Execute in:&amp;quot; entry to the UNC path of the HVS32, with reference to the dispatch station directory (e.g.: \\server\hvs32\Dispatch stations\Dispatch)&lt;/div&gt;</summary>
		<author><name>Lappl</name></author>
	</entry>
</feed>