Ford Motor Company Postcards circa 1917

My father shared a few of these via email I found the entire image set and PDF. Courtesy of Dean’s Garage and Model A Owners of Canada.

Remarkable to see the Ford production table.
Brings to mind Tesla (TSLA) who in 2019 produced ~ 365,300 vehicles.
2019 US population: 329.45 million people.

Ford produced this amount in 1915 (~308,213). Population? 1/3.
1915 US population: 100.55 million people.

PDF version.

1971 Suzuki MT50 TrailHopper

Its been too long.
Small engines are a personal hobby; something I can do with our kids and my father. And its an opportunity to learn from “old” technology. I sincerely enjoy understanding the designs of the past; especially when we can’t implement the simplicity today (e.g. due to emissions).

My father picked this up. A first year, all original, one-owner 1971 Suzuki MT50 Trail-Hopper. Has 2665 miles on it. Included is an old Suzuki ad for this fun little machine (courtesy of CollectorsWeekly).

In the process of getting it back running, I could not locate a Service Manual for the MT50 that was freely available. Its important to pay it forward. Here is a scanned copy of a complete Suzuki Service Manual & Part List for Suzuki MT50 TrailHopper 1971, 1972, & 1973.
The best section? Reed valves and C.C.I. pages 103-108.

1971, 1972, & 1973 Suzuki MT50 Service & Parts Manual

May we take this opportunity to express our appreciation for your continuous efforts in expanding the sales market for our products. At this time we have marketed the Suzuki MT50, which has been made completely new in style and excellent in performance.
The Suzuki MT50 has outstanding mechanisms such as reed valve, Suzuki "C.C.I." system and automatic clutch.
The engine performance has been improved especially in low speed and climbing ability. And also its top speed registers 48-56 k m/h (30-35 mph).
This Service Manual explains, mainly, the principles and construction of these new mechanisms.

The most important items, such as disassembling, assembling, tips on adjusting, maintenance standards and tips on handling, are briefly but clearly described in this Manual.
By making a practice of using this Manual, it will assist you in performing perfect servicing.

October, 1970

Poor Performing Wi-Fi (Slow) after upgrading to Windows 10 Creators Update (1703 or 1709)

After the issues with DSIM in my prior post, this is becoming normal for Microsoft to introduce issues in each release.

I had terrible throughput via wireless. Upgraded/downgraded drivers (Intel 7265ac adapter). Tried everything. Then came across this:
Fix: Slow Wifi Issues After Installing Creators Update

Specifically, “Method 1: Disabling Receive segment coalescing (RSC) on your Wireless Adapter”. Feel free to read more here from Microsoft.

All that said, it was the root cause and disabling RSC resolved the issue.
Summarized steps (borrowing from the linked site above; refer to their site for screenshots):

  1. Launch an elevated Command Prompt
  2. Type powershell Get-Netadapter and note down the value under Name for your Wifi.
  3. Then type, powershell Get-NetAdapterRsc when you do this it will show you the current values, if it is False, then it is already disabled
  4. If it is True, then disable it by typing powershell Disable-NetAdapterRsc -Name WiFi
    Replace the value for -Name with the name of your Wifi.

DSIM Windows 10 Creators Update (1703) Error: 0x800f081f

After being unable to install .NET 3.5 on a clean Windows 10 Pro install, this led me to do a DISM /Online /Cleanup-Image /RestoreHealth which would NOT complete.

Microsoft shipped Creators Update with missing and/or corrupt MUM files (Microsoft Update Manifest, error CBS Corrupt MUM).

Error screenshot:

Follow the guide here or here to resolve.

Basically involves removing the following Registry entries (you have to give yourself “Full Control” before you can delete them). Backup the keys just in case you ever want them.

  1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~
  2. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0


Confirm in an elevated command prompt:

dism.exe /online /cleanup-image /restorehealth

I would suspect millions of Windows 10 Creators Update 64-bit machines suffer this issue and can’t properly add/remove Windows features or repair using DISM.

Windows Server 2008 2012 DHCP Reservations MAC addresses MUST be lowercase!

Came across this silly error while trying to enter DHCP reservations into Server 2012 R2. The issue is not related to the IP being outside the DHCP address pool.

If you try to add an UPPERCASE MAC address:

You get the following (un)helpful warnings:

“The Unique Identifier you have entered may not be correct. Do you
want to use this identifier anyway”

“The DHCP server received a message from a client that is not valid”

Which tells you nothing helpful or informative. After adjusting the Address Pool, it because clear that was not the issue. Using a random MAC address generator, the generated MAC worked without issue. Ironically it was lowercase. I converted my failed MAC address to lowercase and it worked without issue, even outside the Address Pool.

Ideally this saves others a few minutes in their day.

Permanently removing Windows printers that keeps coming back

A simple change: a new Windows print server requiring a change in the printers installed using a Group Policy Targeting GPO (refer to this post from 2015 for more details).

Not so easy. Removing the old/existing printers were all but impossible. Nothing worked. Nothing. Others have had similar experiences; e.g. here, here, and here.

This is a two part post: 1) the actual removal script and 2) other online resources and discussion around the issue.

Removal Script

This script was used as GPO Computer shutdown script.

  1. Download:
  2. Edit the “shutdown_registry_printer_purge.bat” batch file. Go to Line 19 and 20 and change the server name in quotes for both lines. Two lines per printer.
    REM ------------------------------> Add these two lines per printer to remove and change server name <------------------------------
    rundll32 printui.dll,PrintUIEntry /gd /q /n"\\print\PaperCut"
    rundll32 printui.dll,PrintUIEntry /dn /q /n"\\print\PaperCut"
  3. Go to Line 23 and change the server name in quotes. One line per printer.
    REM ------------------------------> Add this one line per printer to remove and change server name <------------------------------
    ADPRINTX.exe /r "\\print\PaperCut"
  4. Edit the “printer_hive_cleanup.vbs” file. Go to Line 117 and 119 and change the server name in quotes for both lines. Two lines per printer.

    A special thanks to Mick for his wonderful vbs script. If you want a less forceful method, Mick also references a way to do per-user registry edit using Active-Setup (I did not test this method).
  5. Add the .bat file to a shutdown or startup script.
    The script must run as the SYSTEM user.

Other Resources on adding/removing Windows printers

  1. Removing a printer device FULLY – Microsoft Community 
  2. group policy – Deleted printers keeps coming back – and multiply – Server Fault 
  3. Problem with multiple instances of shared printers being installed on client computers when the spooler service is started 
  4. [SOLVED] All network printers automatically added for each user on 2012 R2 RDSH – Microsoft Remote Desktop Services – Spiceworks 
  5. Remove Printers by Name or Server – Script Center – Spiceworks 
  6. script to add new network printers 
  7. Set Default Printer if not in a specific group – Petri IT Knowledgebase Forums 
  8. Adding a network printer from the command line (or bat file) – Networking – Spiceworks 
  9. Script to remove obsolete printer in local profiles – Petri
  10. Hey, Scripting Guy! How Can I Remove All the Network Printers on a Computer?
  11. Printer mapping using GPP 
  12. Intermittent printer delivery failures with GPP – XenDesktop 7.x – Discussions 
  13. Logon Script Example Assign Printer – RUNDLL32 PRINTUI.DLL 
  14. scripting – Need to modify VB script so it deletes all existing network printers first – Server Fault 
  15. Adding and deleting printer drivers on Windows from INF files via command-line | Hajuria’s Blog 
  16. KB3170455 preventing printer installation 
  17. command line – Trying to use rundll32 printui.dll, PrintUIEntry to set up a printer, getting an error – Super User 


Search results aren’t quite ready yet, but we’re working on getting them together. Try back in a few minutes.

While I rely on Windows 10, this is classic example of reliability engineering.
Keep it simple.
Because of time constraints, posts will be short and to the point.

Cortana would not index files and as a result, Windows Search was effective non-functional. A clean reinstall with our current set of GPOs caused my domain account to crash Cortana. Even after excluding the suspect GPO, my user profile would still not allow Cortana to index files and Control Panel/Metro settings. The error was: “Search results aren’t quite ready yet, but we’re working on getting them together.  Try back in a few minutes.”

Google tells me many others are having the same issue: here, here, here here, here, and here if you want to read and learn more.
The fix? This assumes United States English. If you want a different language, copy/paste the files from the same location from a system with the identical language; e.g. en-GB

  1. Download: en-US
  2. Extract to:
  3. If extracted correctly, double check the path:
  4. Reboot! Cortana and Window Search should be functional with complete results.

Another option is to remove the ability to search for Windows settings; refer to this thread.

Windows 10 Start Menu Crash/Freeze & Repair

For the reasons Windows 10 is an upgrade, a freezing start menu is beyond frustrating. After rebuilding the Windows Search database, confirming DISM is healthy, did a CHKDSK and System File Checker, I was running out of ideas.

Then I came across this: Reset Windows 10 Start Menu “TileDataLayer”. which led to Fix Windows 10 Start Button Does Nothing in 10 Minutes and a repair tool from Microsoft released in June 2016 (direct link). So this is a known issue.

Before becoming aware of the Microsoft utility, I did my own fix. Using a tool called Unlocker (portable version; part of my digital toolbox) you can forcibly rename/delete files locked by the system. FYI, Unlocker can cause false-positives with anti-virus software. If you are concerned, please upload your downloaded copy to VirusTotal for a second scan.

Using Unlocker, I went to the following location:unlocker_choose_folder


Hit “OK”. Action should be “Rename” and change the name to “DatabaseBackup“.


Finally you should get the following prompt; his “Yes”.


Let the system reboot.
Now – Reboot again – a second time

You will have to recreate your tiles but your start button should at least work and search.

What a mess: Exchange 2013 with Direct Booking and the AutoAccept Agent

In short, Direct Booking and all the associated mailbox delegation controls that were in Exchange 2003 became confusing in 2007 and became a mess in Exchange 2013.

This is a short, reference post.

At this point in time (Mid-2016) most people already experienced this pain but, through these links, I finally tracked down multiple issues with Room Resources not sending Accept/Reject emails to Delegates.

  1. Start with a simple explanation between the old and new ways:  Exchange 2003 Auto Accept Agent vs. direct booking & Booking Delegation Vs. Classic Delegation.
  2. Then use this Powershell script to discover which mailboxes and/or resources have Direct Booking enabled: Use Exchange Web Services and PowerShell to Discover and Remove Direct Booking Settings. Then use the “write” method to actually make the changes to the desired mailboxes. Read the include README file closely for prerequisites.
  3. Simple PowerShell to confirm and modify resources one-by-one: Two ways to grant access to a Resource in #MSFTExchange
  4. Lastly, and because we have a manageable number of Room Resources, go one-by-one and save them using the EAC. Decent double check because in at least one Microsoft Exchange Team blog post they mentioned that EAC does cleanup when it is saved post-upgrade. Specifically, a few rooms under “Booking Delegates” had a setting “Use customized setting to accept or decline booking requests”. Change the Room Resource to either “Accept or decline…” or “Select delegates…”.
    Before: custom booking delegates
    After:booking delegates

 Additional Reading:

  1. Setting Calendar Options For Resource Mailboxes In Exchange 2010…
  2. How to Create and configure a meeting room mailbox with Exchange Server 2007
  3. A Look at Exchange Server 2013 Resource Mailboxes
  4. Working with Resource Mailboxes in Exchange Server 2016
  5. Tool before the PowerShell script above: SetAA – Tweak Auto Accept Settings Across Mailboxes and an article explaining how to use it: Disable Direct Booking For All Room Mailboxes.
  6. I found the last step, saving in EAC, does mailbox cleanup. If not you can manually remove the mailbox from a room resource: I can’t disable a resource mailbox? Sez Who?
  7. Before screenshot above which was not well documented: Resources Booking Delegates Fix (AutomateProcessing: AutoUpdate)
  8. Exchange 2007: Resource delegate never receives forwarded meeting requests for approval 
  9. Useful method for appending information to meeting requests: Using Transport Rules to append text to Meeting Requests when Room Mailbox is selected as Resource

Bypassing “This program cannot run under VMWare or Virtual PC”

We had a specific application that did not want to run on as a virtual machine ( VMWare guest).

Sorry, this application cannot run under a Virtual Machine

“This program cannot run under VMWare or Virtual PC”
“Sorry, this application cannot run under a Virtual Machine”

Tell VMWare to prevent the guest from knowing its a virtual machine (VM).
Kudos to this post on

In this particular situation, all access to the guest was done over Remote Desktop Protocol (RDP); in other words, graphics performance was not critical.

NOTE: The modified VM will have poorer performance, especially with graphics, and VMware Tools will not work. This is an experimental configuration and not advised for long term use.

Shut down your VM. Add the following lines to the .VMX file of your VM (refer to this KB article from VMWare showing how to add these lines to different enciroments; e.g. Workstation, vSphere Client, etc.) = “TRUE” = “TRUE” = “TRUE” = “TRUE”
monitor_control.disable_directexec = “TRUE”
monitor_control.disable_chksimd = “TRUE”
monitor_control.disable_ntreloc = “TRUE”
monitor_control.disable_selfmod = “TRUE”
monitor_control.disable_reloc = “TRUE”
monitor_control.disable_btinout = “TRUE”
monitor_control.disable_btmemspace = “TRUE”
monitor_control.disable_btpriv = “TRUE”
monitor_control.disable_btseg = “TRUE”
tools.upgrade.policy = “manual”
monitor_control.restrict_backdoor = “TRUE”

Power-on your VM. Remove VMWare tools.
The problematic application should launch and run without issue. Enjoy.