How can I disable Windows 7 MSI logging?
I ran CCleaner just now and found that it wanted to free 14 GB from my Windows temp files. I took a look and they are being stored at C:WindowsTemp, and they are some sort of MSI log file. Google tells me these are installation log files, but everything is about how to enable them, and I can't figure out how to disable them. This frequently happens and it sucks up a lot of space on my SSD.
Here's a sampling of the first few lines of the many log files:
=== Verbose logging started: 7/19/2014 2:01:13 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:WindowsMicrosoft.NETFrameworkv4.0.30319mscorsvw.exe ===
MSI (c) (24:F4) [02:01:13:729]: Resetting cached policy values
MSI (c) (24:F4) [02:01:13:729]: Machine policy value 'Debug' is 0
MSI (c) (24:F4) [02:01:13:729]: ******* RunEngine:
******* Product: {9C593464-7F2F-37B3-89F8-7E894E3B09EA}
******* Action:
******* CommandLine: **********
MSI (c) (24:F4) [02:01:13:729]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (24:F4) [02:01:13:729]: Grabbed execution mutex.
MSI (c) (24:F4) [02:01:13:731]: Cloaking enabled.
MSI (c) (24:F4) [02:01:13:731]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (24:F4) [02:01:13:732]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (B4:88) [02:01:13:734]: Running installation inside multi-package transaction {9C593464-7F2F-37B3-89F8-7E894E3B09EA}
MSI (s) (B4:88) [02:01:13:734]: Grabbed execution mutex.
MSI (s) (B4:B8) [02:01:13:735]: Resetting cached policy values
There are hundreds of these files with a name like MSI#####.LOG, with the # being a letter or number. Even if I delete them they come back a few days or weeks later.
I have tried the solution given here to disable the logging but it did not work.
How can I turn these off completely?
windows-7 logging temporary-files
asked Jul 21 '14 at 13:23
ssb
1581313
add a comment |
I ran CCleaner just now and found that it wanted to free 14 GB from my Windows temp files. I took a look and they are being stored at C:WindowsTemp, and they are some sort of MSI log file. Google tells me these are installation log files, but everything is about how to enable them, and I can't figure out how to disable them. This frequently happens and it sucks up a lot of space on my SSD.
Here's a sampling of the first few lines of the many log files:
=== Verbose logging started: 7/19/2014 2:01:13 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:WindowsMicrosoft.NETFrameworkv4.0.30319mscorsvw.exe ===
MSI (c) (24:F4) [02:01:13:729]: Resetting cached policy values
MSI (c) (24:F4) [02:01:13:729]: Machine policy value 'Debug' is 0
MSI (c) (24:F4) [02:01:13:729]: ******* RunEngine:
******* Product: {9C593464-7F2F-37B3-89F8-7E894E3B09EA}
******* Action:
******* CommandLine: **********
MSI (c) (24:F4) [02:01:13:729]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (24:F4) [02:01:13:729]: Grabbed execution mutex.
MSI (c) (24:F4) [02:01:13:731]: Cloaking enabled.
MSI (c) (24:F4) [02:01:13:731]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (24:F4) [02:01:13:732]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (B4:88) [02:01:13:734]: Running installation inside multi-package transaction {9C593464-7F2F-37B3-89F8-7E894E3B09EA}
MSI (s) (B4:88) [02:01:13:734]: Grabbed execution mutex.
MSI (s) (B4:B8) [02:01:13:735]: Resetting cached policy values
There are hundreds of these files with a name like MSI#####.LOG, with the # being a letter or number. Even if I delete them they come back a few days or weeks later.
I have tried the solution given here to disable the logging but it did not work.
How can I turn these off completely?
windows-7 logging temporary-files
asked Jul 21 '14 at 13:23
ssb
1581313
I think the reason you're getting a lot of log files is because some MSI-based setup didn't finish properly. The sample you posted reads:Calling process: C:WindowsMicrosoft.NETFrameworkv4.0.30319mscorsvw.exeThe application is described as .NET Runtime Optimization Service. A few lines later there's a GUID ({9C593464-7F2F-37B3-89F8-7E894E3B09EA}) which appears to be associated with Visual Studio Professional 2013. Related question: Too many log files being created in Temp folder
– and31415
Jul 21 '14 at 15:14
@and31415 Interesting, I'll give that solution a try. If it works I invite anyone to mark this as a duplicate.
– ssb
Jul 21 '14 at 15:18
I'll just note I never found a solution for this. It was definitely connected to a bad Visual Studio installation, so the newer community version might not have this issue. But nevertheless I long ago reformatted and installed Windows 10 and do not have the issue.
– ssb
Feb 9 '16 at 0:36
add a comment |
I ran CCleaner just now and found that it wanted to free 14 GB from my Windows temp files. I took a look and they are being stored at C:WindowsTemp, and they are some sort of MSI log file. Google tells me these are installation log files, but everything is about how to enable them, and I can't figure out how to disable them. This frequently happens and it sucks up a lot of space on my SSD.
Here's a sampling of the first few lines of the many log files:
=== Verbose logging started: 7/19/2014 2:01:13 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:WindowsMicrosoft.NETFrameworkv4.0.30319mscorsvw.exe ===
MSI (c) (24:F4) [02:01:13:729]: Resetting cached policy values
MSI (c) (24:F4) [02:01:13:729]: Machine policy value 'Debug' is 0
MSI (c) (24:F4) [02:01:13:729]: ******* RunEngine:
******* Product: {9C593464-7F2F-37B3-89F8-7E894E3B09EA}
******* Action:
******* CommandLine: **********
MSI (c) (24:F4) [02:01:13:729]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (24:F4) [02:01:13:729]: Grabbed execution mutex.
MSI (c) (24:F4) [02:01:13:731]: Cloaking enabled.
MSI (c) (24:F4) [02:01:13:731]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (24:F4) [02:01:13:732]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (B4:88) [02:01:13:734]: Running installation inside multi-package transaction {9C593464-7F2F-37B3-89F8-7E894E3B09EA}
MSI (s) (B4:88) [02:01:13:734]: Grabbed execution mutex.
MSI (s) (B4:B8) [02:01:13:735]: Resetting cached policy values
There are hundreds of these files with a name like MSI#####.LOG, with the # being a letter or number. Even if I delete them they come back a few days or weeks later.
I have tried the solution given here to disable the logging but it did not work.
How can I turn these off completely?
windows-7 logging temporary-files
asked Jul 21 '14 at 13:23
ssb
1581313
I ran CCleaner just now and found that it wanted to free 14 GB from my Windows temp files. I took a look and they are being stored at C:WindowsTemp, and they are some sort of MSI log file. Google tells me these are installation log files, but everything is about how to enable them, and I can't figure out how to disable them. This frequently happens and it sucks up a lot of space on my SSD.
Here's a sampling of the first few lines of the many log files:
=== Verbose logging started: 7/19/2014 2:01:13 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:WindowsMicrosoft.NETFrameworkv4.0.30319mscorsvw.exe ===
MSI (c) (24:F4) [02:01:13:729]: Resetting cached policy values
MSI (c) (24:F4) [02:01:13:729]: Machine policy value 'Debug' is 0
MSI (c) (24:F4) [02:01:13:729]: ******* RunEngine:
******* Product: {9C593464-7F2F-37B3-89F8-7E894E3B09EA}
******* Action:
******* CommandLine: **********
MSI (c) (24:F4) [02:01:13:729]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (24:F4) [02:01:13:729]: Grabbed execution mutex.
MSI (c) (24:F4) [02:01:13:731]: Cloaking enabled.
MSI (c) (24:F4) [02:01:13:731]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (24:F4) [02:01:13:732]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (B4:88) [02:01:13:734]: Running installation inside multi-package transaction {9C593464-7F2F-37B3-89F8-7E894E3B09EA}
MSI (s) (B4:88) [02:01:13:734]: Grabbed execution mutex.
MSI (s) (B4:B8) [02:01:13:735]: Resetting cached policy values
There are hundreds of these files with a name like MSI#####.LOG, with the # being a letter or number. Even if I delete them they come back a few days or weeks later.
I have tried the solution given here to disable the logging but it did not work.
How can I turn these off completely?
windows-7 logging temporary-files
windows-7 logging temporary-files
asked Jul 21 '14 at 13:23
ssb
1581313
asked Jul 21 '14 at 13:23
ssb
1581313
edited Jul 21 '14 at 14:42
asked Jul 21 '14 at 13:23
ssb
1581313
asked Jul 21 '14 at 13:23
ssb
1581313
asked Jul 21 '14 at 13:23
ssb
1581313
1581313
I think the reason you're getting a lot of log files is because some MSI-based setup didn't finish properly. The sample you posted reads:Calling process: C:WindowsMicrosoft.NETFrameworkv4.0.30319mscorsvw.exeThe application is described as .NET Runtime Optimization Service. A few lines later there's a GUID ({9C593464-7F2F-37B3-89F8-7E894E3B09EA}) which appears to be associated with Visual Studio Professional 2013. Related question: Too many log files being created in Temp folder
– and31415
Jul 21 '14 at 15:14
@and31415 Interesting, I'll give that solution a try. If it works I invite anyone to mark this as a duplicate.
– ssb
Jul 21 '14 at 15:18
I'll just note I never found a solution for this. It was definitely connected to a bad Visual Studio installation, so the newer community version might not have this issue. But nevertheless I long ago reformatted and installed Windows 10 and do not have the issue.
– ssb
Feb 9 '16 at 0:36
add a comment |
I think the reason you're getting a lot of log files is because some MSI-based setup didn't finish properly. The sample you posted reads:Calling process: C:WindowsMicrosoft.NETFrameworkv4.0.30319mscorsvw.exeThe application is described as .NET Runtime Optimization Service. A few lines later there's a GUID ({9C593464-7F2F-37B3-89F8-7E894E3B09EA}) which appears to be associated with Visual Studio Professional 2013. Related question: Too many log files being created in Temp folder
– and31415
Jul 21 '14 at 15:14
@and31415 Interesting, I'll give that solution a try. If it works I invite anyone to mark this as a duplicate.
– ssb
Jul 21 '14 at 15:18
I'll just note I never found a solution for this. It was definitely connected to a bad Visual Studio installation, so the newer community version might not have this issue. But nevertheless I long ago reformatted and installed Windows 10 and do not have the issue.
– ssb
Feb 9 '16 at 0:36
I think the reason you're getting a lot of log files is because some MSI-based setup didn't finish properly. The sample you posted reads:
Calling process: C:WindowsMicrosoft.NETFrameworkv4.0.30319mscorsvw.exe The application is described as .NET Runtime Optimization Service. A few lines later there's a GUID ({9C593464-7F2F-37B3-89F8-7E894E3B09EA}) which appears to be associated with Visual Studio Professional 2013. Related question: Too many log files being created in Temp folder– and31415
Jul 21 '14 at 15:14
I think the reason you're getting a lot of log files is because some MSI-based setup didn't finish properly. The sample you posted reads:
Calling process: C:WindowsMicrosoft.NETFrameworkv4.0.30319mscorsvw.exe The application is described as .NET Runtime Optimization Service. A few lines later there's a GUID ({9C593464-7F2F-37B3-89F8-7E894E3B09EA}) which appears to be associated with Visual Studio Professional 2013. Related question: Too many log files being created in Temp folder– and31415
Jul 21 '14 at 15:14
@and31415 Interesting, I'll give that solution a try. If it works I invite anyone to mark this as a duplicate.
– ssb
Jul 21 '14 at 15:18
@and31415 Interesting, I'll give that solution a try. If it works I invite anyone to mark this as a duplicate.
– ssb
Jul 21 '14 at 15:18
I'll just note I never found a solution for this. It was definitely connected to a bad Visual Studio installation, so the newer community version might not have this issue. But nevertheless I long ago reformatted and installed Windows 10 and do not have the issue.
– ssb
Feb 9 '16 at 0:36
I'll just note I never found a solution for this. It was definitely connected to a bad Visual Studio installation, so the newer community version might not have this issue. But nevertheless I long ago reformatted and installed Windows 10 and do not have the issue.
– ssb
Feb 9 '16 at 0:36
add a comment |
1 Answer
1
active
oldest
votes
Applications and/or the system should not place anything in that directory for long term storage. You should have no issue deleting them.
As for the logging, you can delete the registry setting that turns it on. Go to
Local Computer>Software>Policies>Microsoft>Windows>Installer
If there is a key of "Logging", delete it (maybe write down the value first).
Now if you are on a domain, the admins may force this setting, so you many not be able to do this. Also, various applications will continue to dump data into that directory (Office 365, for sure).
answered Jul 21 '14 at 13:34
KingOfAllTrades
234139
Thanks for the answer. I'm looking at HKEY_LOCAL_MACHINE>SOFTWARE>Policies>Microsoft>Windows, but there's no Installer. Is this the right place to be looking?
– ssb
Jul 21 '14 at 13:39
Yes, that is the correct path. I see it in my registry. Hmmm... Maybe you could add it with minimal logging and see if it reduces it? Add a key "Logging" with the value "mo" and that may reduce the amount logged (only out of disk and out of memory errors).
– KingOfAllTrades
Jul 21 '14 at 14:12
The "Installer" key is not there by default, you have to enable it. support.microsoft.com/en-us/help/223300/…
– HelpingHand
Sep 24 '17 at 9:44
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f785833%2fhow-can-i-disable-windows-7-msi-logging%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Applications and/or the system should not place anything in that directory for long term storage. You should have no issue deleting them.
As for the logging, you can delete the registry setting that turns it on. Go to
Local Computer>Software>Policies>Microsoft>Windows>Installer
If there is a key of "Logging", delete it (maybe write down the value first).
Now if you are on a domain, the admins may force this setting, so you many not be able to do this. Also, various applications will continue to dump data into that directory (Office 365, for sure).
answered Jul 21 '14 at 13:34
KingOfAllTrades
234139
Thanks for the answer. I'm looking at HKEY_LOCAL_MACHINE>SOFTWARE>Policies>Microsoft>Windows, but there's no Installer. Is this the right place to be looking?
– ssb
Jul 21 '14 at 13:39
Yes, that is the correct path. I see it in my registry. Hmmm... Maybe you could add it with minimal logging and see if it reduces it? Add a key "Logging" with the value "mo" and that may reduce the amount logged (only out of disk and out of memory errors).
– KingOfAllTrades
Jul 21 '14 at 14:12
The "Installer" key is not there by default, you have to enable it. support.microsoft.com/en-us/help/223300/…
– HelpingHand
Sep 24 '17 at 9:44
add a comment |
Applications and/or the system should not place anything in that directory for long term storage. You should have no issue deleting them.
As for the logging, you can delete the registry setting that turns it on. Go to
Local Computer>Software>Policies>Microsoft>Windows>Installer
If there is a key of "Logging", delete it (maybe write down the value first).
Now if you are on a domain, the admins may force this setting, so you many not be able to do this. Also, various applications will continue to dump data into that directory (Office 365, for sure).
answered Jul 21 '14 at 13:34
KingOfAllTrades
234139
Thanks for the answer. I'm looking at HKEY_LOCAL_MACHINE>SOFTWARE>Policies>Microsoft>Windows, but there's no Installer. Is this the right place to be looking?
– ssb
Jul 21 '14 at 13:39
Yes, that is the correct path. I see it in my registry. Hmmm... Maybe you could add it with minimal logging and see if it reduces it? Add a key "Logging" with the value "mo" and that may reduce the amount logged (only out of disk and out of memory errors).
– KingOfAllTrades
Jul 21 '14 at 14:12
The "Installer" key is not there by default, you have to enable it. support.microsoft.com/en-us/help/223300/…
– HelpingHand
Sep 24 '17 at 9:44
add a comment |
Applications and/or the system should not place anything in that directory for long term storage. You should have no issue deleting them.
As for the logging, you can delete the registry setting that turns it on. Go to
Local Computer>Software>Policies>Microsoft>Windows>Installer
If there is a key of "Logging", delete it (maybe write down the value first).
Now if you are on a domain, the admins may force this setting, so you many not be able to do this. Also, various applications will continue to dump data into that directory (Office 365, for sure).
answered Jul 21 '14 at 13:34
KingOfAllTrades
234139
Applications and/or the system should not place anything in that directory for long term storage. You should have no issue deleting them.
As for the logging, you can delete the registry setting that turns it on. Go to
Local Computer>Software>Policies>Microsoft>Windows>Installer
If there is a key of "Logging", delete it (maybe write down the value first).
Now if you are on a domain, the admins may force this setting, so you many not be able to do this. Also, various applications will continue to dump data into that directory (Office 365, for sure).
answered Jul 21 '14 at 13:34
KingOfAllTrades
234139
answered Jul 21 '14 at 13:34
KingOfAllTrades
234139
answered Jul 21 '14 at 13:34
KingOfAllTrades
234139
answered Jul 21 '14 at 13:34
KingOfAllTrades
234139
234139
Thanks for the answer. I'm looking at HKEY_LOCAL_MACHINE>SOFTWARE>Policies>Microsoft>Windows, but there's no Installer. Is this the right place to be looking?
– ssb
Jul 21 '14 at 13:39
Yes, that is the correct path. I see it in my registry. Hmmm... Maybe you could add it with minimal logging and see if it reduces it? Add a key "Logging" with the value "mo" and that may reduce the amount logged (only out of disk and out of memory errors).
– KingOfAllTrades
Jul 21 '14 at 14:12
The "Installer" key is not there by default, you have to enable it. support.microsoft.com/en-us/help/223300/…
– HelpingHand
Sep 24 '17 at 9:44
add a comment |
Thanks for the answer. I'm looking at HKEY_LOCAL_MACHINE>SOFTWARE>Policies>Microsoft>Windows, but there's no Installer. Is this the right place to be looking?
– ssb
Jul 21 '14 at 13:39
Yes, that is the correct path. I see it in my registry. Hmmm... Maybe you could add it with minimal logging and see if it reduces it? Add a key "Logging" with the value "mo" and that may reduce the amount logged (only out of disk and out of memory errors).
– KingOfAllTrades
Jul 21 '14 at 14:12
The "Installer" key is not there by default, you have to enable it. support.microsoft.com/en-us/help/223300/…
– HelpingHand
Sep 24 '17 at 9:44
Thanks for the answer. I'm looking at HKEY_LOCAL_MACHINE>SOFTWARE>Policies>Microsoft>Windows, but there's no Installer. Is this the right place to be looking?
– ssb
Jul 21 '14 at 13:39
Thanks for the answer. I'm looking at HKEY_LOCAL_MACHINE>SOFTWARE>Policies>Microsoft>Windows, but there's no Installer. Is this the right place to be looking?
– ssb
Jul 21 '14 at 13:39
Yes, that is the correct path. I see it in my registry. Hmmm... Maybe you could add it with minimal logging and see if it reduces it? Add a key "Logging" with the value "mo" and that may reduce the amount logged (only out of disk and out of memory errors).
– KingOfAllTrades
Jul 21 '14 at 14:12
Yes, that is the correct path. I see it in my registry. Hmmm... Maybe you could add it with minimal logging and see if it reduces it? Add a key "Logging" with the value "mo" and that may reduce the amount logged (only out of disk and out of memory errors).
– KingOfAllTrades
Jul 21 '14 at 14:12
The "Installer" key is not there by default, you have to enable it. support.microsoft.com/en-us/help/223300/…
– HelpingHand
Sep 24 '17 at 9:44
The "Installer" key is not there by default, you have to enable it. support.microsoft.com/en-us/help/223300/…
– HelpingHand
Sep 24 '17 at 9:44
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f785833%2fhow-can-i-disable-windows-7-msi-logging%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I think the reason you're getting a lot of log files is because some MSI-based setup didn't finish properly. The sample you posted reads:
Calling process: C:WindowsMicrosoft.NETFrameworkv4.0.30319mscorsvw.exeThe application is described as .NET Runtime Optimization Service. A few lines later there's a GUID ({9C593464-7F2F-37B3-89F8-7E894E3B09EA}) which appears to be associated with Visual Studio Professional 2013. Related question: Too many log files being created in Temp folder– and31415
Jul 21 '14 at 15:14
@and31415 Interesting, I'll give that solution a try. If it works I invite anyone to mark this as a duplicate.
– ssb
Jul 21 '14 at 15:18
I'll just note I never found a solution for this. It was definitely connected to a bad Visual Studio installation, so the newer community version might not have this issue. But nevertheless I long ago reformatted and installed Windows 10 and do not have the issue.
– ssb
Feb 9 '16 at 0:36