1 files changed, 57 insertions, 0 deletions
diff --git a/results/classifier/118/graphic/1839294 b/results/classifier/118/graphic/1839294
new file mode 100644
index 000000000..ab27cf347
--- /dev/null
+++ b/results/classifier/118/graphic/1839294
@@ -0,0 +1,57 @@
+graphic: 0.865
+files: 0.821
+device: 0.720
+semantic: 0.671
+ppc: 0.634
+performance: 0.595
+architecture: 0.577
+socket: 0.448
+assembly: 0.421
+network: 0.401
+arm: 0.400
+permissions: 0.384
+vnc: 0.376
+hypervisor: 0.359
+PID: 0.356
+register: 0.341
+kernel: 0.335
+user-level: 0.316
+mistranslation: 0.313
+boot: 0.268
+peripherals: 0.266
+TCG: 0.258
+VMM: 0.219
+risc-v: 0.208
+debug: 0.200
+KVM: 0.182
+x86: 0.146
+virtual: 0.144
+i386: 0.103
+
+Latest Installer (qemu-w64-setup-20190807.exe) for windows immediately deletes installed files at the very end of the installation
+
+This happens on Windows 10 with the latest installer for 64 bit Windows: qemu-w64-setup-20190807.exe
+
+On install it will create the files and go through all the typical functions of installing the software, at the very end step it will then delete all files the installer created.
+
+I looked for logs to see when was going on so I ran the installation in Sandboxie and was able to retain all the installed files but I couldn't find a log for the installer.
+
+Here is a screenshot of it deleting all the files at the end of the process.
+
+https://imgur.com/BWiTA38
+
+If goes too fast for me to see what is written in the text console otherwise I would post more information but this is all I have. It does not give any error or any other information at completion.
+
+This error does not occur in the earlier release: qemu-w64-setup-20190731.exe
+
+
+
+I hit the same error in my azure pipelines script that uses `choco install qemu`. While it worked with qemu-w64-setup-20190731.exe, the `C:\Program Files\qemu` directory is empty with qemu-w64-setup-20190807.exe.
+
+We can forget this one if nothing happens from now on; however, this problem might have a rare but systemic problem. We can always wait and see if this problem is ever duplicated. In which case there is at least a commonality to the bug.
+
+Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
+
+
+[Expired for QEMU because there has been no activity for 60 days.]
+