Running TD on windows 10. Worked fine until closing out TD after running StreamDIffusion successfully. Would not restart after several attempts . Reinstalled/restart does not provide a proper icon, (blank text page) and still doesn’t run. Help? Note that both the user and the system environmental paths to find the exe. etc are correct.
Are you attempting to open a specific file or just TouchDesigner default session? What do you mean “does not provide a proper icon”?
in means that instead of the usual TD desktop icon which activates the program I get an icon that looks like a text icon. I have many TD programs . I am just opening professional app with a dongle but first I’m trying simply to open the app and then d=bring in the programs etc. So even without the dongle nothing happens. If you want to take over this system remotely you can but I’ve done all the obvious things.
You should never need to reinstall TouchDesigner, unless you were changing files or something in the installation directory. But that does some like something is wrong with your intallation. I would re-download TouchDesigner installer and and do a full uninstall from “Add / Remove Programs” (assuming you are on WIndows). Then restart your system before installing TouchDesigner again.
Have reinstalled a couple of times. Same issue. Hate to mess with the Registry but check if there’s an issue.It seems the exe file may be getting corrupted even after reinstall.
I’ve assigned this question to one of our devs who works with the installer. Due to time zones I don’t think he’ll reply until tomorrow.
Its a long shot, but if you have any Window Updates awaiting install, I’d apply them. Sometimes this patches up Windows when it goes sideways.
The only update left is win 11 and this is not what we need to do at this point. As you can read from the initial we are on win10 and have had no previous problems.
Understood. No reason for the move to 11, its was just worth checking.
OK thanks.
Hi @Anthony_Gerber,
If you are running on a AMD machine with integrated graphics, please make sure to update the driver via AMD Adrenalin.
looking for more information that might give some clues to how to resolve your issue:
- the TouchDesigner Installation does not usually set any user or system environment paths. Was this done manually and what are the values in there?
- when uninstalling TouchDesigner, was the Codemeter software removed as well?
- when starting TouchDesigner, can you see it in the Task Manager as a process?
- does the TouchDesigner.exe in the installation folder show the textfile icon as well or does it show the expected TouchDesigner icon?
- do project (
.toe) or component files (.tox) still have their expected icons? - what version of TouchDesigner are you using?
The Installer’s registry changes are fairly basic just setting up the application id and associating recognized filetypes like .toe and similar.
If you want to check the registry and clean it out, any TouchDesigner references should be in HKA/Software/Classes/TouchDesigner*** as well as HKCR/Local Settings/Software/Microsoft/Windows/Shell/MuiCache
cheers
Markus
Many thanks for the thoughtful reply. In fact the .exe issue when we investigated further affected other major programs such Maya and Adobe etc. so clearly an OS issue. I’m not sure what created the problem initially but suspects include downloads from Git and perhaps python and other open source material we are using in TD Commercial. Running he “exe” file [c:\access .exe=exefile] resulted in denial of access for all “exe” execution. The fix is to reinstall the OS (in this case Win10) which can be done by running a Microsoft Media Creation Tool after downloading the program. This preserves both apps and data but its still prudent to back up all before running it. Dongle unaffected. Icons now as expected and active. So apologies for the fire drill but perhaps the process of repair is useful for others. It should be noted that there are also c:\DISM type instructions that can be used to find/correct corrupted file in the OS but this doesn’t always result in a solution. Best to run the recovery tool.
Many thanks again for the prompt support.
Tony
1 Like