Windows 7

How to Fix 80244019 Windows Update Error - Windows 7

The 80244019 Windows Update error message is usually caused by a registry setting for a WSUS server. If you are no longer using the WSUS server or it is not online, you can simply delete the registry key and all of its subkeys to resolve the problem. As always with registry changes, make a backup of the registry before you delete anything:

HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

Restart the "Windows Update" service after deleting the key. You may also have to restart, but most likely not. This may work on Windows XP as well, but I haven't tested it yet.

How to Fix - Windows Update Cannot Check for Updates - Controlled by Administrator Windows 7

You may see the following error message when manually checking for Windows Updates on Windows 7:

Windows Update Cannot Check for Update Controlled by Administrator

This is usually intended behavior, caused by a policy from an administrator. To remove this policy and check for updates and install them, change the following registry entry from 1 to 0:

HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\NoWindowsUpdate

HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\NoWindowsUpdate

HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\WindowsUpdate\DisableWindowsUpdateAccess

You should be able to check for updates now. No restart required!

How to Change Last Logged on User at Windows 7 Login Screen in Registry

After logging onto a Windows 7 computer, your username will be displayed on the login screen after a restart or logoff, like this:

Change last logged in user on windows 7 login screen

Whether working remotely or locally, you may not want the next person to login to the computer to know you were logged into it. The 2 main reasons are:

  1. Security - The user may not want you in their computer and they would question you if they knew you were in it.
  2. Login Trouble - Many users do not know how to switch user accounts on Windows 7, and they may spend 30 minutes trying to login before they call you for help!

To change the last logged in user at the Windows 7 login screen, simply edit the following registry entry and restart the computer:

HKLM\Software\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\LastLoggedOnUser

For a domain account, make sure to put it in this format: DOMAIN\username

Windows 7 - Path to All Users Desktop and All Users Start Menu

"Where is the All Users Desktop and All Users Start Menu folders in Windows 7 and why did they change it?" is probably the question you are asking yourself right now. I'm not really sure why they changed it, but I do know the path to where they are located:

All Users Desktop Folder:

C:\Users\Public\Desktop\

All Users Start Menu Folder:

C:\ProgramData\Microsoft\Windows\Start Menu\

In Explorer, you need to check "Show Hidden Files" at Tools > Folder Options > View in order to view these folders. Alternatively, you can just type the full path in Explorer or the Run box.

---------------------------------------------------------------------------------------------------------------------------------

Missing your windows desktop while you`re away from the work? Now retain your windows desktop experience with remote accessibility to your preferred windows applications on high performance hosted citrix xendesktop from CloudDesktopOnline at an unbelievable xendesktop cost. Visit Apps4Rent.com to learn more about hosted SharePoint, Exchange, MS Project Server, Dynamics CRM and Azure managed services.

Windows 7 - Migrate Local Profiles to Domain Profiles in 5 Steps and 5 Minutes Using Registry Tweak

Don't waste hours using time consuming profile migration tools when you can do it in minutes using a simple registry tweak. This technique can be used to migrate local profiles to domain profiles, domain profiles to local profiles, and domain profiles to domain profiles. It simply involves modifying a registry value and changing the permissions on the user directory and registry hives. In my example, I will be migrating a local profile on Windows 7 to a domain profile. My local user's account name is "user" and my domain user's account name is "tuser". The local user is part of the Local Administrators group. The Domain User is not part of the Local Administrators group, but it won't matter if it is (This tutorial was tested with UAC turned off.) If you or your company finds this tutorial useful, helpful, or time saving, please consider making a donation with the paypal link on the right. This helps with the authors time and hosting bills. Thanks

This has been tested on many production and test environments. In our test environment, here is a list of customizations and software installed and configured on the local user's account:

How to Download and Run a Program in Windows 7 With IE9 - 6 Step Tutorial

Downloading a program/executable in Windows 7 is as easy as 1, 2, 3, 4, 5, and 6! Just follow this simple tutorial, and you will be downloading applications in no time!

Step 1: ​In your web browser (also know as "The Internet" or "Internet Explorer") click on a download link:

ie9_download_file1

​Step 2: ​Click on "Actions":

ie9_download_file2

​Step 3: Click on "Run":

ie9_download_file3

​Step 4: ​A SmartScreen Filter dialog box will open. Click on the downward pointing triangle next to "More Options":

ie9_download_file4

​Step 5: ​Click on "Run anyway":

ie9_download_file5

​Step 6: A User Account Control dialog box will open. Click on Yes:

ie9_download_file6

Fix for Can't RDP into 2008 R2 or Windows 7 after Update 2667402 and SP1 - Remote Desktop Services Stops

If you arrived at this page, it is likely because you can't use Remote Desktop Protocol to remote into a Wndows 7 or Server 2008 R2 system. The Remote Desktop Services is stopped, and everytime you enable it, it crashes. You also receive an error message like this in the Application event log:

2667402rdp2008r2-2"Faulting application name: svchost.exe_TermService, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1

Faulting module name: rdpcorekmts.dll, version: 6.1.7600.16952, time stamp: 0x4f1f9e66
Exception code: 0xc0000005
Fault offset: 0x000000000000a793
Faulting process id: 0xabc
Faulting application start time: 0x01cd4a68213a1459
Faulting application path: C:\Windows\System32\svchost.exe
Faulting module path: C:\Windows\system32\rdpcorekmts.dll

This is a known issue and will occur if you are running Windows 7 or Server 2008 R2, apply update 2667402, and then install Service Pack 1. After you install security update 2667402, and then you install SP1, the binary version of Rdpcorekmts.dll is 6.1.7600.16952 and not 6.1.7601.17767. This issue occurs because the SP1 binary version of Rdpcorekmts.dll was not originally deployed when security update 2667402 was originally installed.

How to Uninstall Internet Explorer 9 on Windows 7 SP1 and Revert to IE8

Windows 7 with service pack 1 comes loaded with Internet Explorer 9 by default. You can revert to Internet Explorer 8 by following theses steps:

  • Open "Programs and Features", formerly called "Add or Remove Programs", by clicking on the start button (or by holding down "Windows key + R" to bring up the run menu) and typing appwiz.cpl and hit enter. Click on "View installed  updates":Internet Explorer 9 Remove 1
  • Select "Windows Internet Explorer 9" from the update list and click "Uninstall" Internet Explorer 9 Remove 2
  • Reboot your computer and you will have Internet Explorer 8

How to Change the Desktop Icon Size on Windows 7 and Vista

Changing the size of the desktop icons is very easy in Windows 7. Click anywhere on the desktop, then simply hold down the Ctrl key and scroll the mouse wheel up or down to increase or decrease the size. You may not prefer to have your icons 1/4 the size of you monitor, but sneak over to your co-workers computer while he is on lunch break and change theirs. See how long it takes them to figure it out:

icon_large

icon_small

Fix error 0x000006D9 on Windows 7 and Server 2008 R2 - Sharing Printer

If you are trying to share a printer on Windows 7 or Server 2008 R2, you may experience this error:

0x000006D9

This issue occurs because the Spooler services uses the Firewallapi.dll file to make an API call to check the availability of the Windows Firewall service. If you experience this error, you must have the firewall enabled in order to share out the printer. This only seems to affect network printers, not locally attached printers.

To enable the firewall:

Start > Run > firewall.cpl > Turn Windows Firewall on or off > Turn on Firewall for the type of network location you use

As far as I can tell, you can turn the firewall back off after you share the printer and it will not mess up the printer sharing.

http://support.microsoft.com/kb/2123653

Pages

Subscribe to Windows 7