Cleaning windows - logs

Generally you can delete them after a successful hardware or software installation but they are littered all over the place. Puran Utilities is good for finding lots of them but it doesn't find these in C:\Windows\inf.

Here we're going to look at these on three notebooks all running windows 7 Home Premium.
This is a screenshot from Red.

Blue shows the last two files at 14,158,258 & 952,217  which is nuts as there's nothing much on it. What is even nutser is that Black only has setupapi.app.log and it's 159 bytes.

There is an interesting article at https://support.microsoft.com/en-ph/help/958909/it-takes-a-long-time-to-log-on-to-a-windows-vista-based-computer-that which states that anything over 5Mb is very large and suggests that the reason is verbose reporting and mainly caused by anti-virus software continually opening and closing the log file.

Well I dunno about that but changing the value of
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Setup\LogLevel

certainly has an effect, to whit:

The verbosity of the log report is set by that registry key, in the old days it was 20000FFFF, the article above suggests using 20. I have no idea how Black ended up with 101 but it works and boots in 45s so it's staying as it is.

Blue now boots in 2¼  minutes rather than 15 or so and is usable again. Same spec as Black, a pretty basic AMD C-60, 1000 MHz, 4Gb RAM.

Red's much the same as before, it's an old i7 but still pretty quick.

If you're not comfortable with editing the registry then don't; the adventurous might like to rename 

setupapi.app.log & setupapi.dev.log 

to

setupapi.app.logOLD & setupapi.dev.logOLD

reboot and see what happens.

The file size reductions above are after the first reboot, whether they grow remains to be seen.

All machines are using AVG Anti-virus, the free version.
Stop press: changing the Blue verbosity to 101 reduces startup to 2 minutes and the log file is now 10,831

I don't know why setupapi.app.20170521_151423.log and setupapi.dev.20150729_121527.log are in blue. They seem to be snapshots from the past but they're gone and not missed.

---

Puran Utilities  - I'm using v 3.0.0.0 from 2013, the latest version may do a bit more. If you install it check the folder for oddities. I've just noticed this massive Temp file

now that's gone too.

Digging a bit deeper, there's a file called AppList which works with Delete History

So that can be edited to add stuff or hide what you never use. Clever or what?

---

Happy Cleaning

Cleaning windows - PED and WER

The first bit's about Power Efficiency Diagnostics, Windows Error Reporting is but a click away
Disclaimer

Power Efficiency Diagnostics is a program run by Task Scheduler. It may be useful in helping you set up a laptop but other than that it justs wastes disc space.
In any case you have to check the results yourself, there is no automation.
In any case² you have to know it exists.

Below I cleaned out a million or so .xml files but left the energy-report-latest.xml file after reading dire warnings on the web. I renamed the energy-ntkl.etl then manually started Power Efficiency Diagnostics.

So it still works ok but let's kill it

Do

Start Menu - Programs - Accessories - System Tools

and run

Task Scheduler

Find \Microsoft\Windows\Power Efficiency Diagnostics

Right click and choose Disable

Now you can clean out the detritus in C:\ProgramData\Microsoft\Windows\Power Efficiency Diagnostics

Windows Error Reporting is something to do with sending crash logs to you-know-who after programs have failed.

Go to C:\ProgramData\Microsoft\Windows\WER and see something like this

Open those folders delete all the files, then use Task Scheduler to disable the program

Tada........

Disclaimation - It works for me on Windows 7, better make sure you know how to do a Windows Restore first.
Be sure to read the next instalment

Back to the top

Dehydrating fruit - part 6 - using a tray liner

A glut of tomatoes in the Southern Annex

2018 and a very hot summer has produced an enormous crop which is too much to eat  fresh so I decided to dry some.
Preparation was wash, slice about ¹/₂" (12.7 mm) thick, remove the hard cores.
Various sources on the www recommend using a tray liner to avoid dripping onto the tray below and sticking.
The options:

• Excalibur sheets at £7 a pop
• 9 Chuzy Chef sheets for £10.99 + 4.49 p&p
• 5 NUTRIDRY mesh sheets for £16.95 + 3.95 p&p
• Plastic Canvas from the local craft shop £3 each, probably not food safe
• Teflon baking sheet from the cupboard £0.

So the last one won and you can see the result in the graph below.

The absence of airflow on the lower surface reduced the rate of drying dramatically so out it came and that tray went on to more or less catch up with the others.
In the final analysis, sticking wasn't a problem and the tomatoes came off easily.

The dehydrator ran overnight on cheap juice so they were moon dried - a world first. Some were drier than others so they all went into a sealed container overnight to balance out the moisture then they were wrapped in cling film and frozen in batches.
I tasted one and it was almost a sultana.
Initial weight  3168g.

---