Closed GoogleCodeExporter closed 9 years ago
I expect that the .NET Framework Update can't replace some files while they are
used. But this would be more a bug in the .NET Framework Updates then in the
Open Hardware Monitor.
We need more evidence that the Open Hardware Monitor is doing something wrong
for this issue (and of course what it is doing wrong).
Original comment by moel.mich
on 23 Jun 2010 at 7:01
Original comment by moel.mich
on 23 Jun 2010 at 7:10
I just installed these .NET Framework Updates on my Windows 7 x64 machine (as
suggested by Windows Update). I had the Open Hardware Monitor running all the
time while the update was installed, and the installation was successful. The
update requested a restart, during which the updated was completed, and the
Open Hardware Monitor also autostarted correctly after booting.
Original comment by moel.mich
on 23 Jun 2010 at 6:21
Interesting - I had attempted the update a number of times with it consistently
failing - The only change I made was to close OHM and it worked fine. Maybe
just a fluke, but thought it was worth mentioning. I appreciate you looking
into it - perhaps updating to the latest beta (think I'm 1 version behind atm)
would've resolved it as well.
I love the software, it's been very handy for me so thank you guys a bunch for
making it.
Original comment by ldaula...@gmail.com
on 23 Jun 2010 at 6:52
Original comment by moel.mich
on 23 Jan 2011 at 7:37
Original issue reported on code.google.com by
ldaula...@gmail.com
on 22 Jun 2010 at 9:53