As the title points out, I'm almost ready to release WURT v.5 Beta. It's a huge improvement, both in internal code organization and actual capability. I'll post a change log here in the blog when I post the executable, but the biggest improvements are command-line switches and network time synchronization.

I'm still looking for Vista testers. I know no one actually reads my blog, but just in case, if anyone should stumble across any time soon, please email me at WURT@hitoma.com.

I'm also working on another tool, a derivative of the research behind WURT. It still needs a bit of work before I release a very early beta, but think of it as a passive WURT that runs in the background. It's called WRS, and I'll go into more detail soon.

Labels: programs, services, vista, windows update, wrs, wurt

I'm finally getting back to WURT to a decent degree. Quite a few of the features I've wanted to add for a while, like command line switches, net time updating, and Windows Vista detection, have been added in. It's still beta, but it's much better.

Expect a release and a full changelog within the next few days.

On another note, if anyone would like to beta test WURT v.5 on Windows Vista, please let me know at wurtbeta@hitoma.com.

Labels: programs, vista, windows update, wurt

A new WURT beta is available at the WURT Homepage. It's a bit redesigned and more stable, and also offers to completely reinstall Internet Explorer. I'm currently recommending anyone using on a previous version to upgrade to it.

Also, you may have noticed the new design on the WURT site. It's only temporary: I'm working on a new design for the entire site, and possibly more content. I've got a couple of little programs in the works, so stop back soon.

Labels: programs, windows update, wurt

I've found an interesting bug in Windows XP Home. It's well known that one of the removed features in XP Home is the Group Policy Editor, gpedit.msc. It's a pretty useful tool, as any administrator will tell you, but it's not necessary for home use.

However, although the editor is unavailable to you, the settings it creates are still perfectly valid. So, if I track the change gpedit.msc makes on a Pro machine, export it, and import it on a Home machine, if that effect isn't specific to Pro, it'll affect the Home machine.

I found this out while scrubbing some systems at work of malware. I've had two in the last week that were XP Home machines that you could not change Windows Firewall settings on from the Security Center. Go into the Firewall control panel, and you'll be greeted with a happy message.

For your security, some settings are controlled by Group Policy.

One of my coworkers figured that it had hit that registry setting, and sure enough, it had. Removing the key fixed the issue. But there are a ton of far-reaching settings in gpedit, and the effects of this could be disastrous. Realistically, Microsoft should either release a gpedit for XP Home, or release a patch (or twenty) for home that disables checks to this key.

If you have a similar issue, the key is:

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\WindowsFirewall\StandardProfile\EnableFirewall

1 = firewall forced on
0 = firewall forced off
no key = manual control enabled

I'm going to integrate the ability to disable this key into the next version of WURT. I feel that it's worth integrating and is relatively pertinent. I may also make a tool just to fix this.

WURT .4 Beta should be available in just a day or two. It'll also have a few fixes, although nothing for the annoying History/Temp folder cleaning bug. Most of the changes aren't visible, but it's much more efficient now.

Labels: programs, windows update, wurt

I've created an actual page for WURT. You can see it at:

http://software.hitoma.com/WURT/

In other news, this blog has been updated multiple times in the last few days. I'm pretty sure that's a sign of the apocalypse.

Labels: programs, windows update, wurt

Since this blog may come up on search results about Windows Update issues, I'm going to release a temporary beta. It doesn't expire, I'm not responsible if anything bad should happen, and it isn't finished or perfect by any means.

Disclaimer: No, I really mean it. It may not fix your issue. It may break your computer. Your PC could catch on fire. Maybe you hair. Heck, this program could ruin your love life. Meteors could strike the earth! It could cause the end of time! No matter what happens, it's not my fault. Use at your own risk!!! I mean it.

That said, if you get an error message, please email me with the EXACT text of the message. There are a couple of errors that mention CCleaner that I do not need to be told about - they'll almost always occur. It may also need you to download runtime files - I'll try to post those, but email me about it in the meantime.

Daunted yet? Good. Give it a shot, and email me if it works for you, too.

Download that file by right-clicking on it and choosing Save Target As... in IE, or a similar option if you are smart and use Firefox or the new Netscape 8.

I'll have source available when the project is stable. If you want to help, use an email link above.

Labels: programs, windows update, wurt

My new utility, the Windows Update Repair Tool, is coming along nicely. I've gotten some much needed assistance from my esteemed colleague here at Clarion University, Joshua Rhoades. He's currently reworking a couple of sections for maintainability and efficiency, but when that's done I will likely post a beta version.

Currently, it can fix about 75% of all issues I know about. While it currently runs as a console Win32 application, I may make a GUI version. I'd eventually like to make a 'catch' version - if Windows Update encountered an error, WURT would automatically repair it. This would require some cooperation from Microsoft, however, so before I make any attempt WURT needs to mature a bit. Such a feature may only be feasible on Windows XP SP2, however, so that feature is a long way off.

I'm considering using a special license combining the GPL and Spybot's license. Stay tuned.

In other news, I had a car accident in my Kia Spectra. Going around a bend, I hit some anti-skid (basically gravel used for traction on icy roads), and started spinning on a main road. I went at least one whole rotation, hitting the hill on the side of the road, and ended up sideways across the road. I quickly drove into a factory driveway, then got out to assess the damage The damage to my car isn't major, and the insurance will cover it. My passenger and I were unhurt, but that's merely due to the luck of no other traffic coming - at that spot, both directions are somewhat blinded, so it could have been pretty bad.

Labels: programs, windows update, wurt