Useless result.html File Constantly Created Version 14.0 Build 130

Jamil-Taylor wrote on 12/30/2020, 2:26 AM

I have been wondering what application installed on my workstation is constantly creating a result.html file on the root of my D: drive. I just recently learned that it is Sound Forger version 14.0 creating this file. I delete the file and it gets created again every day. It is creating two files: result.html and result.xml

Why is SoundForge creating this result.html file that contains no content on a daily basis? It is an empty file containing 1 byte that is simply a new line. It also creates result.xml that is 69 bytes that contains the following:

<?xml version="1.0" encoding="UTF-8"?>
<response><patch/></response>

How do I stop it from doing this? Old versions of Sound Forge never did this, so this is some fairly recent change (perhaps when MAGIX purchased the product).

Comments

rraud wrote on 12/30/2020, 9:18 AM

Is SF installed on your D:\ drive? Is it affecting performance in any way? If it is just an annoyance, hide it. I have no idea why it is there or it's function, Sorry. Ask Magix Tech Support.

Jamil-Taylor wrote on 12/30/2020, 9:51 AM

Sound Forge is installed at the default installer locations:

C:\Program Files\SOUND FORGE

C:\Program Files (x86)\SOUND FORGE

It writes these two files several times per day. I deleted them both earlier, and they both returned. Is it a performance issue? Most likely yes. What is worst is that these unneeded files being written over and over will reduce the lifetime of SSD media.

I will report this bug to tech support as you suggest.

johnebaker wrote on 12/30/2020, 1:16 PM

@Jamil-Taylor

. . . . Is it a performance issue? Most likely yes. . . . .

No, IIRC the files are generated when the software is updated and started to record any issues that may prevent the next update installing. They must be present for when the next update occurs which is why they are regenerated when you delete them.

. . . . What is worst is that these unneeded files being written over and over will reduce the lifetime of SSD media. . . . .

These files, which are harmless, take up very little space and will have no impact on the life time of the SSD drive. If you are concerned about SSD life then Windows should not be installed on one - the paging file alone will use up write cycles much faster then writing these two small files.

Writing data at a rate of 150 - 200 GB/day to a SSD drive and hard drive - the SSD will out last the hard drive, the times an SSD drive does fail is mainly ,due to the controller failing not the number of write cycles, and any memory cells that do fail a write are automatically removed from the pool of available cells.

John EB

Jamil-Taylor wrote on 12/30/2020, 6:00 PM

Are you suggesting that this is working as designed?

Why is result.html and result.xml being written to D:\ each and every time I start Sound Forge? This looks like a defect to me.

Jamil-Taylor wrote on 3/10/2021, 12:21 AM

Is SF installed on your D:\ drive? Is it affecting performance in any way? If it is just an annoyance, hide it. I have no idea why it is there or it's function, Sorry. Ask Magix Tech Support.

Note that I did exactly as you suggested. I opened a support request for the version I had installed. I got an email from support to share screenshots showing these two files being created. The support person stated he would share this with development for a fix. The issue was never fixed, and it remains today for version 14.

I just installed the latest version of 15 that was just released. This version also contains this defect. Support closed my ticket without it being fixed, and the bug is still present in their code base.

emmrecs wrote on 3/10/2021, 4:38 AM

@Jamil-Taylor

In his reply to you @johnebaker pointed out what these files are for and hence why they are created. In no sense can I see that this could be called a "bug" since their purpose is apparently to ensure that any future update proceeds without problem

Jeff
Forum Moderator

Jamil-Taylor wrote on 3/10/2021, 5:00 AM

@Jamil-Taylor

In his reply to you @johnebaker pointed out what these files are for and hence why they are created. In no sense can I see that this could be called a "bug" since their purpose is apparently to ensure that any future update proceeds without problem

Jeff
Forum Moderator

Support acknowledged that this is incorrect and should not be present that disagrees what what you stated above. This is misinformation.

emmrecs wrote on 3/10/2021, 5:24 AM

@Jamil-Taylor

Since Support have apparently confirmed this should not be happening I am happy to stand corrected!

Jeff

Jamil-Taylor wrote on 3/10/2021, 5:26 AM

@Jamil-Taylor

Since Support have apparently confirmed this should not be happening I am happy to stand corrected!

Jeff

Okay. What are my next steps to take? I tried visiting support, they acknowledged the issue then closed my ticket.