# \[Bug-7829\] Ignition upgrade to 8.1.28 failed

**URL:** <https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [June 3, 2023, 8:28am UTC](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527 "2023-06-03T08:28:50Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![zxcslo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zxcslo/32/61610_2.png) [@zxcslo](https://forum.inductiveautomation.com/u/zxcslo)\
**Post date:** [June 3, 2023, 8:28am UTC](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527/1 "2023-06-03T08:28:50Z")

</div>

Today I was trying to upgrade my Ignition from 8.1.27 to 8.1.28 and the gateway won't start:  
 ![Screenshot_19](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/7/477bd8dea02a9a60b839db67bd57d1697f1965a6.png)

> **Summary**
>
> ```auto
> STATUS | wrapperm | 2023/06/03 10:19:01 | Starting the Ignition Gateway service...
> STATUS | wrapper | 2023/06/03 10:19:01 | --> Wrapper Started as Service
> STATUS | wrapper | 2023/06/03 10:19:01 | Java Service Wrapper Standard Edition 64-bit 3.5.42
> STATUS | wrapper | 2023/06/03 10:19:01 | Copyright (C) 1999-2020 Tanuki Software, Ltd. All Rights Reserved.
> STATUS | wrapper | 2023/06/03 10:19:01 | http://wrapper.tanukisoftware.com
> STATUS | wrapper | 2023/06/03 10:19:01 | Licensed to Inductive Automation for Inductive Automation
> STATUS | wrapper | 2023/06/03 10:19:01 | 
> STATUS | wrapper | 2023/06/03 10:19:02 | Launching a JVM...
> INFO | jvm 1 | 2023/06/03 10:19:02 | WrapperManager: Initializing...
> INFO | jvm 1 | 2023/06/03 10:19:02 | 10:19:02,758 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [data\\logback.xml] at [file:/C:/Program%20Files/Inductive%20Automation/Ignition/data/logback.xml]
> INFO | jvm 1 | 2023/06/03 10:19:02 | 10:19:02,827 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
> INFO | jvm 1 | 2023/06/03 10:19:02 | 10:19:02,828 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [SysoutAppender]
> INFO | jvm 1 | 2023/06/03 10:19:02 | 10:19:02,831 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
> INFO | jvm 1 | 2023/06/03 10:19:02 | 10:19:02,844 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [com.inductiveautomation.logging.SQLiteAppender]
> INFO | jvm 1 | 2023/06/03 10:19:02 | 10:19:02,850 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [DB]
> INFO | jvm 1 | 2023/06/03 10:19:03 | 10:19:02,955 |-INFO in ch.qos.logback.core.db.DataSourceConnectionSource@5f9b188e - Driver name=SQLite JDBC
> INFO | jvm 1 | 2023/06/03 10:19:03 | 10:19:02,956 |-INFO in ch.qos.logback.core.db.DataSourceConnectionSource@5f9b188e - Driver version=3.41.2.1
> INFO | jvm 1 | 2023/06/03 10:19:03 | 10:19:02,956 |-INFO in ch.qos.logback.core.db.DataSourceConnectionSource@5f9b188e - supportsGetGeneratedKeys=true
> INFO | jvm 1 | 2023/06/03 10:19:03 | 10:19:02,963 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.AsyncAppender]
> INFO | jvm 1 | 2023/06/03 10:19:03 | 10:19:02,964 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [SysoutAsync]
> INFO | jvm 1 | 2023/06/03 10:19:03 | 10:19:02,964 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [SysoutAppender] to ch.qos.logback.classic.AsyncAppender[SysoutAsync]
> INFO | jvm 1 | 2023/06/03 10:19:03 | 10:19:02,965 |-INFO in ch.qos.logback.classic.AsyncAppender[SysoutAsync] - Attaching appender named [SysoutAppender] to AsyncAppender.
> INFO | jvm 1 | 2023/06/03 10:19:03 | 10:19:02,965 |-INFO in ch.qos.logback.classic.AsyncAppender[SysoutAsync] - Setting discardingThreshold to 51
> INFO | jvm 1 | 2023/06/03 10:19:03 | 10:19:02,967 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.AsyncAppender]
> INFO | jvm 1 | 2023/06/03 10:19:03 | 10:19:02,967 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [DBAsync]
> INFO | jvm 1 | 2023/06/03 10:19:03 | 10:19:02,967 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [DB] to ch.qos.logback.classic.AsyncAppender[DBAsync]
> INFO | jvm 1 | 2023/06/03 10:19:03 | 10:19:02,967 |-INFO in ch.qos.logback.classic.AsyncAppender[DBAsync] - Attaching appender named [DB] to AsyncAppender.
> INFO | jvm 1 | 2023/06/03 10:19:03 | 10:19:02,967 |-INFO in ch.qos.logback.classic.AsyncAppender[DBAsync] - Setting discardingThreshold to 51
> INFO | jvm 1 | 2023/06/03 10:19:03 | 10:19:02,969 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to INFO
> INFO | jvm 1 | 2023/06/03 10:19:03 | 10:19:02,969 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [SysoutAsync] to Logger[ROOT]
> INFO | jvm 1 | 2023/06/03 10:19:03 | 10:19:02,969 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [DBAsync] to Logger[ROOT]
> INFO | jvm 1 | 2023/06/03 10:19:03 | 10:19:02,969 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
> INFO | jvm 1 | 2023/06/03 10:19:03 | 10:19:02,970 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@683c594c - Registering current configuration as safe fallback point
> INFO | jvm 1 | 2023/06/03 10:19:03 | 10:19:02,996 |-INFO in ch.qos.logback.classic.jul.LevelChangePropagator@414f8a82 - Propagating INFO level on Logger[ROOT] onto the JUL framework
> INFO | jvm 1 | 2023/06/03 10:19:03 | E [IgnitionGateway] [08:19:03]: Error initializing web manager:  
> INFO | jvm 1 | 2023/06/03 10:19:03 | java.lang.IllegalArgumentException: Malformed \uxxxx encoding.
> INFO | jvm 1 | 2023/06/03 10:19:03 | at java.base/java.util.Properties.loadConvert(Unknown Source)
> INFO | jvm 1 | 2023/06/03 10:19:03 | at java.base/java.util.Properties.load0(Unknown Source)
> INFO | jvm 1 | 2023/06/03 10:19:03 | at java.base/java.util.Properties.load(Unknown Source)
> INFO | jvm 1 | 2023/06/03 10:19:03 | at com.inductiveautomation.ignition.gateway.web.WebResourceManagerImpl.readInstallProperties(WebResourceManagerImpl.java:447)
> INFO | jvm 1 | 2023/06/03 10:19:03 | at com.inductiveautomation.ignition.gateway.web.WebResourceManagerImpl.<init>(WebResourceManagerImpl.java:113)
> INFO | jvm 1 | 2023/06/03 10:19:03 | at com.inductiveautomation.ignition.gateway.IgnitionGateway.<init>(IgnitionGateway.java:523)
> INFO | jvm 1 | 2023/06/03 10:19:03 | at com.inductiveautomation.ignition.gateway.IgnitionGateway.main(IgnitionGateway.java:298)
> INFO | jvm 1 | 2023/06/03 10:19:03 | at com.inductiveautomation.catapult.Catapult.main(Catapult.java:8)
> INFO | jvm 1 | 2023/06/03 10:19:03 | at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> INFO | jvm 1 | 2023/06/03 10:19:03 | at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> INFO | jvm 1 | 2023/06/03 10:19:03 | at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> INFO | jvm 1 | 2023/06/03 10:19:03 | at java.base/java.lang.reflect.Method.invoke(Unknown Source)
> INFO | jvm 1 | 2023/06/03 10:19:03 | at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:349)
> INFO | jvm 1 | 2023/06/03 10:19:03 | at java.base/java.lang.Thread.run(Unknown Source)
> INFO | jvm 1 | 2023/06/03 10:19:03 | WrapperSimpleApp: 
> INFO | jvm 1 | 2023/06/03 10:19:03 | WrapperSimpleApp Error: Encountered an error running main:
> INFO | jvm 1 | 2023/06/03 10:19:03 | WrapperSimpleApp Error: java.lang.NullPointerException
> INFO | jvm 1 | 2023/06/03 10:19:03 | WrapperSimpleApp Error: at com.inductiveautomation.ignition.gateway.IgnitionGateway.start(IgnitionGateway.java:578)
> INFO | jvm 1 | 2023/06/03 10:19:03 | WrapperSimpleApp Error: at com.inductiveautomation.ignition.gateway.IgnitionGateway.main(IgnitionGateway.java:300)
> INFO | jvm 1 | 2023/06/03 10:19:03 | WrapperSimpleApp Error: at com.inductiveautomation.catapult.Catapult.main(Catapult.java:8)
> INFO | jvm 1 | 2023/06/03 10:19:03 | WrapperSimpleApp Error: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> INFO | jvm 1 | 2023/06/03 10:19:03 | WrapperSimpleApp Error: at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> INFO | jvm 1 | 2023/06/03 10:19:03 | WrapperSimpleApp Error: at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> INFO | jvm 1 | 2023/06/03 10:19:03 | WrapperSimpleApp Error: at java.base/java.lang.reflect.Method.invoke(Unknown Source)
> INFO | jvm 1 | 2023/06/03 10:19:03 | WrapperSimpleApp Error: at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:349)
> INFO | jvm 1 | 2023/06/03 10:19:03 | WrapperSimpleApp Error: at java.base/java.lang.Thread.run(Unknown Source)
> INFO | jvm 1 | 2023/06/03 10:19:03 | I [C.SecureRandomProvider] [08:19:03]: Secure random seed generated in 0ms 
> STATUS | wrapper | 2023/06/03 10:19:05 | <-- Wrapper Stopped
> ERROR | wrapperm | 2023/06/03 10:19:06 | The Ignition Gateway service was launched, but failed to start.
> ERROR | wrapperm | 2023/06/03 10:19:06 | Please check the log file for more information: C:\Program Files\Inductive Automation\Ignition\logs\wrapper.log
> 
> ```

I downgraded back to 8.1.27 and the gateway is starting normal...  
I also tried 8.1.29 SNAPSHOT and the gateway also won't start...

This is on Windows x64 2016 LTSB... (on VMWare Virtual machine)...

---

<div class="post-metadata">

**Author:** ![zxcslo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zxcslo/32/61610_2.png) [@zxcslo](https://forum.inductiveautomation.com/u/zxcslo)\
**Post date:** [June 3, 2023, 10:10am UTC](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527/2 "2023-06-03T10:10:13Z")

</div>

OK, I found that if I delete the `IgnitionGateway.exe` file from `C:\Program Files\Inductive Automation\Ignition` folder, then the 8.1.28 installation goes through OK and the gateway will start normally.  
But then, if I start the 8.1.28 installation AGAIN and upgrade, the gateway will NOT start.  
And if I delete the `IgnitionGateway.exe` again and start the 8.1.28 install, the gateway will start... 😕

---

<div class="post-metadata">

**Author:** ![avaughn](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/avaughn/32/38972_2.png) [@avaughn](https://forum.inductiveautomation.com/u/avaughn)\
**Post date:** [June 4, 2023, 3:53am UTC](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527/3 "2023-06-04T03:53:40Z")

</div>

Could you upload your install.log and install-info.txt files from after the upgrade? The log file should be in the `logs` folder and install-info.txt is in the `lib` folder.

---

<div class="post-metadata">

**Author:** ![zxcslo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zxcslo/32/61610_2.png) [@zxcslo](https://forum.inductiveautomation.com/u/zxcslo)\
**Post date:** [June 4, 2023, 5:24am UTC](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527/4 "2023-06-04T05:24:51Z")

</div>

There is NO install.log created for this upgrade...  
There are only the old install logs from previous upgrades...  
 ![Screenshot_20](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/2/d2b6e9ced8da248c3910ec48f768fd4a1785332a.png)  
And this is the `install-info.txt`:  
 ![Screenshot_21](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/d/5d1ce9b344a4c9cd831f9c8a241d2744548d56a9.png)

---

<div class="post-metadata">

**Author:** ![zxcslo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zxcslo/32/61610_2.png) [@zxcslo](https://forum.inductiveautomation.com/u/zxcslo)\
**Post date:** [June 4, 2023, 5:41am UTC](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527/5 "2023-06-04T05:41:43Z")

</div>

I found another log file in the user `.ignition` folder...  
[install.log](https://forum.inductiveautomation.com/uploads/short-url/r5rphDfoK6BEcveK5yuNjiN0BJf.log) (149.2 KB)

---

<div class="post-metadata">

**Author:** ![avaughn](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/avaughn/32/38972_2.png) [@avaughn](https://forum.inductiveautomation.com/u/avaughn)\
**Post date:** [June 4, 2023, 6:35am UTC](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527/6 "2023-06-04T06:35:21Z")

</div>

I’ll have to look into it more on Monday, but it seems like it may be failing due to the backslash in the username.

Is the username showing as the same on 8.1.27?

---

<div class="post-metadata">

**Author:** ![zxcslo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zxcslo/32/61610_2.png) [@zxcslo](https://forum.inductiveautomation.com/u/zxcslo)\
**Post date:** [June 4, 2023, 6:41am UTC](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527/7 "2023-06-04T06:41:50Z")

</div>

> [@avaughn](#):
>
> Is the username showing as the same on 8.1.27?

~~Yes.~~  
Actualy NO. See the post bellow...

---

<div class="post-metadata">

**Author:** ![zxcslo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zxcslo/32/61610_2.png) [@zxcslo](https://forum.inductiveautomation.com/u/zxcslo)\
**Post date:** [June 4, 2023, 7:08am UTC](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527/8 "2023-06-04T07:08:15Z")

</div>

You're right.  
If I delete `DESKTOP-8T2EMTA\` from the username in `install-info.txt`, then the Ignition service will start normally...

---

<div class="post-metadata">

**Author:** ![zxcslo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zxcslo/32/61610_2.png) [@zxcslo](https://forum.inductiveautomation.com/u/zxcslo)\
**Post date:** [June 4, 2023, 7:23am UTC](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527/9 "2023-06-04T07:23:57Z")

</div>

This is the `install-info.txt` before upgrade:  
 ![before_upgrade](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/4/243918a8dcd833dae64f111607fb890cebb6f1c6.png)

and this is after upgrade:  
 ![after_upgrade](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/4/a45d830d6e2179ba143e717b2615a51c08d76755.png)  
and the Ignition service won't start.  
If I delete `DESKTOP-8T2EMTA\` from username, then the Ignition service will start.

---

<div class="post-metadata">

**Author:** ![avaughn](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/avaughn/32/38972_2.png) [@avaughn](https://forum.inductiveautomation.com/u/avaughn)\
**Post date:** [June 5, 2023, 2:03pm UTC](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527/10 "2023-06-05T14:03:11Z")

</div>

I was able to replicate this, and it's the `\u` that's tripping it up. This will also happen on 8.1.27, so I'm curious as to why `DESKTOP-8T2EMTA\` was added to the username. From what I see, it gets added when using a specific user account to run the Ignition service.

Between the installation of 8.1.27 and the upgrade to 8.1.28 did you change the account the Ignition service is running as?

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/0/40a52bc63f98a444ed5e8c593bc9af8a5ed760f6.png)

---

<div class="post-metadata">

**Author:** ![zxcslo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zxcslo/32/61610_2.png) [@zxcslo](https://forum.inductiveautomation.com/u/zxcslo)\
**Post date:** [June 5, 2023, 4:10pm UTC](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527/11 "2023-06-05T16:10:48Z")

</div>

No. Service is always running as System (default).

I tried with various upgrades, from 8.1.21, 8.1.23, 8.1.26 and 8.1.27 to 8.1.28 and it's always the same:  
Prior to upgrade, the username is without PC name and backslash, after the upgrade to 8.1.28, PC name and backslash are added...

---

<div class="post-metadata">

**Author:** ![avaughn](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/avaughn/32/38972_2.png) [@avaughn](https://forum.inductiveautomation.com/u/avaughn)\
**Post date:** [June 5, 2023, 4:17pm UTC](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527/12 "2023-06-05T16:17:44Z")

</div>

I filed an internal ticket to get this addressed, but it looks like the optimal solution is to escape the `\u` with a second backslash.

---

<div class="post-metadata">

**Author:** ![jcoffman](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jcoffman/32/6429_2.png) [@jcoffman](https://forum.inductiveautomation.com/u/jcoffman)\
**Post date:** [June 5, 2023, 4:18pm UTC](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527/13 "2023-06-05T16:18:53Z")

</div>

> [@avaughn](#):
>
> but it looks like the optimal solution is to escape the `\u` with a second backslash.

This works and the easiest way is to supply the [`user` CLI argument](https://docs.inductiveautomation.com/display/DOC81/Command+Line+Installations) during install

---

<div class="post-metadata">

**Author:** ![zxcslo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zxcslo/32/61610_2.png) [@zxcslo](https://forum.inductiveautomation.com/u/zxcslo)\
**Post date:** [June 5, 2023, 4:21pm UTC](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527/14 "2023-06-05T16:21:37Z")

</div>

You mean, until this is resolved from your (IA) side...?

---

<div class="post-metadata">

**Author:** ![jcoffman](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jcoffman/32/6429_2.png) [@jcoffman](https://forum.inductiveautomation.com/u/jcoffman)\
**Post date:** [June 5, 2023, 4:59pm UTC](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527/15 "2023-06-05T16:59:44Z")

</div>

Yes. The ticket is filed already, but this will get you up and running in the mean time.

---

<div class="post-metadata">

**Author:** ![avaughn](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/avaughn/32/38972_2.png) [@avaughn](https://forum.inductiveautomation.com/u/avaughn)\
**Post date:** [June 5, 2023, 5:29pm UTC](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527/16 "2023-06-05T17:29:42Z")

</div>

> [@zxcslo](#):
>
> Service is always running as System (default).

Do you have the "Allow service to interact with desktop" option selected?

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/f/afd1bbdc6415b0332fdb960b65029534042033d8.png)

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [June 5, 2023, 5:39pm UTC](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527/17 "2023-06-05T17:39:46Z")

</div>

> [@avaughn](#):
>
> Do you have the "Allow service to interact with desktop" option selected?

Curious. I was under the impression that that setting was a no-op now-a-days.

---

<div class="post-metadata">

**Author:** ![zxcslo](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zxcslo/32/61610_2.png) [@zxcslo](https://forum.inductiveautomation.com/u/zxcslo)\
**Post date:** [June 5, 2023, 5:50pm UTC](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527/18 "2023-06-05T17:50:01Z")

</div>

No, never.

---

<div class="post-metadata">

**Author:** ![avaughn](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/avaughn/32/38972_2.png) [@avaughn](https://forum.inductiveautomation.com/u/avaughn)\
**Post date:** [June 5, 2023, 5:50pm UTC](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527/19 "2023-06-05T17:50:03Z")

</div>

I'll be completely honest, I've never even noticed that option before and don't know anything about it. Checking it though did seem to cause the username to update during install/upgrade to include the user origin and backslash.

Edit: I see from [this](https://forum.inductiveautomation.com/t/interacting-with-desktop/44443) thread that it's mentioned after Windows 7 it isn't really usable.

---

<div class="post-metadata">

**Author:** ![avaughn](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/avaughn/32/38972_2.png) [@avaughn](https://forum.inductiveautomation.com/u/avaughn)\
**Post date:** [June 5, 2023, 8:06pm UTC](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527/20 "2023-06-05T20:06:52Z")

</div>

Not sure why `DESKTOP-8T2EMTA\` is getting added in the first place then. I did do some testing and noticed that once it started to get added during upgrades, I had to restart my entire system to get it to stop.

Ultimately, for now the best thing to do is to manually set the username so it doesn't include the `\u` or escape it with an extra `\`. Or change the user name to not start with `u`. Then once the fix is in place in a future update, you won't have to worry about it.

[Next page](https://forum.inductiveautomation.com/t/bug-7829-ignition-upgrade-to-8-1-28-failed/74527.md?page=2)
