Re: WLSetup creates empty folders in %localappdata%

Most likely a 'current version check/request' i.e. CVC/CVR. I think we saw
something similar in the past during the 2008 to 2009 transition.

Fyi...I've had at least one a day for the last few days and have wiped
those folder(s) most recently as last week(about a dozen).
I'm not configured to 'Help improve Windows Live' on this unit (using
version xx.x.xxxx.1109).


--
....winston
msft mvp mail

"Ildhund" wrote in message news:ig5lel$eph$...


I have an enquiry about this out over at windowslivehelp.com with a
startling absence of response, so perhaps I have a unique problem.

WLSetup seems to be performing a twice-daily check for updates, conducted
by wlshim.dll. The only evidence of this is an accumulation of log files at
%localappdata%\Microsoft\WLSetup\Logs, which say more or less the same day
after day. This is fair enough, even though it seems a bit excessive
considering the frequency of program updates we've seen in the past five
years. What is more alarming is that each one of these spawns an empty
folder in the %localappdata% folder; here's a recent screenshot. While I
can't swear that it's the update process that's creating them, the timings
are precisely the same.

Is anyone else seeing this? Perhaps only those submitting SQM data?
--
Noel

OK, thanks. Good to hear it's not just me. I find it amazing, though, that the programmers don't just add a couple of lines of code
to delete the folder once they're finished with it.
--
Noel

Yes...it would be nice if they addressed some of the sloppyness.

There’s also the possibility that data is being collected on the version to correlate WLE downloads vs. WLM version usage, impact if a mandatory upgrade(e.g. security) was necessary, etc..



--
....winston
msft mvp mail

"Ildhund" wrote in message news:ig70ek$ote$...


OK, thanks. Good to hear it's not just me. I find it amazing, though, that the programmers don't just add a couple of lines of code to delete the folder once they're finished with it.
--
Noel