Yet another ‘Microsoft enhanced Point and Print compatibility driver…’ error

After installing the updates for Windows Server 2012r2 on March 11, I began to get a new set of errors on rebooting that were associated with the Microsoft enhanced Point and Print compatibility driver. These new errors referred to a problem with ‘Unable to find core dependency (see additional info for driver GUID)‘. I did a search for the GUID in the registry and it seemed to point to the Terminal Server Easy Print. Since all the printers I used were network based and installed on all systems, I decided to disable Terminal Server Easy Print.

I found hints on how to disable the Terminal Server Easy Print on Asitha’s Blog but the actual Group Policy settings were in a bit different place on Windows Server 2012r2. After launching the Group Policy editor, gpedit.msc, go to

Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Printer Redirection\Use Remote Desktop Easy Print printer driver first – Disable

and

User Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Printer Redirection\Use Remote Desktop Easy Print printer driver first – Disable

And on reboot the errors were gone…for now.

 

Posted in Windows Server 2012r2 | Leave a comment

Other helpful links for Windows 7 OS and applications

  • If you want to send batch files or command files using Microsoft Office Outlook you need to first configure the registry to unblock attachments. There is a very nice write up here on how to do it.
  • Per Dwarf, even if you log in as an Administrator, you are still running with a token that grants you standard privileges. To actually run in administrative mode, you need to elevate so that you are running with the administrative token. This is a problem when running certain .reg files since the merge functionality can’t be elevated. The solution is to create a batch file and Run as administrator which is described by Dwarf here.
Posted in Windows 7 for development | Leave a comment

Replacing the door lock actuator motor

I’ve had to replace two of the door lock actuators on my 2004 Acura MDX. I wasn’t sure how long they were broken because their failure mode was to not lock instead of not unlocking. The first time it was the rear passenger door and the second time it was the front passenger door.

It seems that the motor burns out and you can just replace it but I went the route of replacing the entire actuator assembly which was about $35. The part number for all the actuators except the driver’s front is 72115-S84-A11 and the drivers front is 72155-S84-A11

The rear actuator was a lot easier than the front actuator.

Posted in 2004 Acura MDX | Leave a comment

Cabin/pollen filter replacement

Since the thermal fuse burnt out in my blower motor on my 2004 Acura MDX, I make sure to change the cabin/pollen filter on schedule. I do this because some people have suggested that when the filter gets clogged there is not enough air flow to keep the thermal fuse cool and it burns out. I’m not completely sure if that is true but changing the filer is much easier than changing the thermal fuse.

This first time changing the cabin/pollen filter actually requires some modification to the car which is best explained in this post. Also, I try to always buy genuine Honda air filter assemblies because they seem to fit better. The part number is 80290-S0X-A01 and usually costs about $27 delivered.

Posted in 2004 Acura MDX | Leave a comment

AC/Heater blower motor stops working for front or back units

Over the ten years of owning my 2004 Acura MDX both the front and rear blower motors have stopped working. The air conditioning also stopped working but that was a different problem where the clutch seized up.

Anyway, both blower motors had the same problem, their thermal fuses burned out. I purchased replacement thermal fuses from DigiKey for about $.75 and thermal paste from Radio Shack.

Unfortunately the front and rear thermal fuses are in quite different places but I found excellent tutorials for the front thermal fuse here and for the back fuse here.

Posted in 2004 Acura MDX | Leave a comment

Loud squeal from engine compartment when cold

My 2004 Acura MDX recently started making a loud squeal when it was cold. Usually it went away when the car warmed up but for short trips it was pretty constant. Also moving the steering wheel changed the pitch of the sound so I was pretty sure it had something to do with the power steering.

Nevertheless, since the car had over over 100,00 miles on it and was almost 10 years old, just to be safe, I had the timing belt and water pump serviced. Since the sound remained, I began looking into what it would take to change the power steering pump and I found a TSB for the Power Steering Moans or Whines During Cold Start-Up.

I kind of doubted that changing the o-ring would fix such a loud noise, but I went ahead and purchased the o-ring (13.0×1.9) part# : 91345-RDA-A01 for $.70 from my local dealer along with some genuine Honda power steering fluid. I followed the TSB instructions to replace the o-ring  and also changed most of the power steering fluid. It took a total of about 30 minutes and unbelievably the sound was gone.

Posted in 2004 Acura MDX | Leave a comment

Ipod connection to factory RES system

I was looking for a simple way to connect the audio out/headphone jack of my iPod to the AUX audio of the DVD Rear Entertainment System in my 2004 Acura MDX. The option existed of using a long cable plugged into the Auxiliary inputs on the third row, but for simplicity and ease of use, I much preferred having the connector mounted by the shifter between the cup holders.

After looking at many different dash mountable input jacks, I settled on the iSimple IS335 Dash Mountable Auxiliary Input Adapter from Amazon.

Using the MDX DVD Player Unit Connector Replacement diagram, and a DVM, I determined that B3 was the right audio signal, B4 the left audio signal, and B8 the audio ground. I used T-Splices and solder to attach the connector wires after I made sure which wires were the left and right channels and cut the RCA connectors off. I could also have used a Solderless Wire Quick Splice Connector.

Since the new audio inputs are in parallel with the rear AUX jacks, the rear AUX jacks work fine when nothing is plugged into the new connector. And to play music from the iPod select DVD/AUX on the head unit.

Posted in 2004 Acura MDX | Leave a comment

Problems with Windows Gadgets

First, I would like to state that I know Microsoft has said gadgets are a bad idea and that there are better alternatives out there. But I do development under Windows 7 and there are a few gadgets that I use everyday and like. For example, the weather gadget and the analog clock with the second hand.

So that being said, it seemed that every couple of days the gadgets wouldn’t start. Initially I tried to fix it with a Reset_Gadgets batch file as presented by Shawn Brink. This worked fine but I wanted to automate the fix so I checked what actually was needed. After some experimentation, it seemed that only killing and restarting the sidebar.exe application was necessary for the gadgets to reappear.

Looking around I found a post by garycase which mentions the problem as being the system booting ‘too fast’ and provides a ‘GadgetsFix.cmd’ to solve the problem. After removing the gadget’s auto-start registry key:

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run] “Sidebar”=”C:\\Program Files\\Windows Sidebar\\sidebar.exe /autoRun”

I put ‘GadgetsFix.cmd’ in the start-up folder C:\Users\xxx\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup and while there was the occasional blinking of the gadgets on start-up they always seemed to appear. However, now I would get a Service not available error from the weather gadget every few days.

According to Aaron – G, the problem was fixed by deleting the settings.ini file or by doing just about everything Shawn Brink was doing in his batch file. So while going back to the Reset_Gadgets batch file was certainly an option, I looked more into the settings.ini angle and what I found was that if the config.xml file was saved without making any changes, the gadget services could connect again. Well, this sounded like the config.xml just needed to be ‘touched’ for it to work so I found a little dos command that performs a ‘touch’

COPY /B %1+,, %1

and put it into a batch file. I then edited the batch file ‘GadgetsFix.cmd’ by garycase to include the touch.cmd file and everything seems to work pretty consistently. Here is my edited ‘GadgetsFix.cmd’

@echo off
timeout 2
tasklist /FI “IMAGENAME eq sidebar.exe” 2>NUL | find /I /N “sidebar.exe”>NUL
IF “%ERRORLEVEL%”==”0” (
taskkill /f /im:sidebar.exe
) else (
call touch “C:\Users\xxx\AppData\Local\Microsoft\Windows Live\Services\Cache\Config.xml”
start “” “%ProgramFiles%\Windows Sidebar\sidebar.exe”
)

timeout 1
tasklist /FI “IMAGENAME eq sidebar.exe” 2>NUL | find /I /N “sidebar.exe”>NUL
IF “%ERRORLEVEL%”==”0” (
taskkill /f /im:sidebar.exe
)
else (
call touch “C:\Users\xxx\AppData\Local\Microsoft\Windows Live\Services\Cache\Config.xml”
start “” “%ProgramFiles%\Windows Sidebar\sidebar.exe”
)

exit

Posted in Windows 7 for development | Leave a comment

Windows Store failed to sync machine licenses

Another error I was getting on my Windows Server 2012r2 x64 machine was:

Windows Store failed to sync machine licenses. Result code 0x80070490.

The solution I found that fixed this error was posted by streetwolf which was to disable the WSRefreshBannedAppsListTask task in the Task Scheduler. The Task Scheduler is found in Computer Management -> System Tools.

Posted in Windows Server 2012r2 | Leave a comment

Windows Search Service – Crawl could not be completed on content…

At random times on Windows Server 2012r2 x64, usually after rebooting, I would get a warning from the Windows Search Service (xxx added to make the error less specific):

Crawl could not be completed on content source <winrt://{S-1-5-21-24xxxxxx66-12xxxxx84-2xxxxxxxx9-1001}/>.

Context:  Application, SystemIndex Catalog

Details:
    The parameter is incorrect.  (HRESULT : 0x80070057) (0x80070057)

The solution for me to fix this warning was to go into the group policy editor and add the offending folder to the default excluded paths list.

  1. Run gpedit.msc
  2. In Local Group Policy Editor, Select Computer Configuration -> Administrative Templates -> Windows Components -> Search.
  3. In Search, double click on Default excluded paths.
  4. In Default Excluded Paths, First select Enabled in the upper left corner. Then click on the  Show… button next to ‘Default Excluded Paths’.
  5. In Show Contents, add “winrt://{S-1-5-21-24xxxxxx66-12xxxxx84-2xxxxxxxx9-1001}/” (without quotes) and then click OK

Next force Windows Search Service to re-index.

  1. Stop the service using services.mscWindows Search or from Administrator: Command Prompt – net stop wsearch
  2. Edit the registry key HKLM/Software/Microsoft/Windows/Search/SetupCompletedSuccessfully and set it to 0
  3. Start the service using services.mscWindows Search or from Administrator: Command Prompt – net start wsearch

 

Posted in Windows Server 2012r2 | Leave a comment