Posts Tagged ‘Windows 7’

Sysprep a Windows 7 Machine – Start to Finish V2

Monday, January 18th, 2010

SPREAD THE WORD, TOGETHER WE HAVE CONQUERED SYSPREP :)

Sorry for the delay, I have been struggling the past couple months with a pinched nerve in my neck. This is version 2 of a step by step guide on Sysprepping a Windows 7 machine from start to finish. I cannot take full credit on this because my first article had so many helpful comments and discussions that this is simply a combination of all the good advice written into a working guide. (I would especially like to thank George for his input on Cscript for auto activation and Nathan for input on Sysprep Audit Mode). This will guide you through the following:

- Audit Mode
- Building the unattended XML file in WSIM
- copyprofile=true command to copy the default profile (no manual copy)
- Prompt for a computer name
- Enable Administrator account
- Administrator account logs in first time automatically
- Activate windows automatically with Cscript;
- Delete sysprep XML file automatically upon completion of re-image.

Here is a list of what you will need:

- Latest version of WAIK : KB3AIK_EN.iso Version 1.0
- Windows Vista or Windows 7 Machine to build the XML file on
- ISO or DVD of Windows 7 Installation (x32 or x64)
- WinPE Boot Environment : BrianLeeJackson WinPE 3.0 BootLoader

First we are going to walk through building the XML file (answer file) and then we will walk through the actual Windows 7 imaging process.

PART 1 – XML FILE CREATION

Step #1

If you have a Windows 7 installation DVD, insert it now. Or if you have an ISO of 7, go ahead and extract it to a folder on your desktop. (I recommend 7-zip).

Step #2

Launch Windows System Image Manager. Your start menu should look like the image below:

Windows 7 WAIK Version 1

Windows 7 WAIK Version 1

Step #3

Under the “Windows Image” header, right click and select new image.

Windows System Image Manager

Windows System Image Manager

Step #4

You will now want to browse to the .CLG file in your Windows 7 installation (I am using Windows 7 Enterprise x64 in my example). It is located in the sources folder. See Image below. You can select either the .clg file or the install.wim. Both will have the same result.

Selecting CLG File - WSIM

Selecting CLG File - WSIM

Step #5

Now we need to create a new answer file. Go to the file menu and select “Create New Answer File.” Right after creating one, go ahead and simply go to file menu and select “Save Answer File.” This will give your XML file a name and save location. Now you see we have two category folders, Components and Packages. Under the Components folder you see that we have 7 options:

-1 windowsPE
-2 offlineServicing
-3 generalize
-4 specialize
-5 auditSystem
-6 auditUser
-7 oobeSystem

Step #6

These are very important as these are the steps in which the XML file is sequenced.
The next part is a little confusing. You are going to add components, from under the “Windows Image” section on the bottom left hand side to the passes on your Answer File. To add a component, you can right click on them and select “add to # pass”. There are many different options you can add, but they have to be done in a certain order and pass otherwise your sysprep might fail. I am simply going to use the one I created as the example.

Answer File - Sysprep XML

Answer File - Sysprep XML

Here is more information about adding options under the passes:

1 windowsPE

Nothing required in my example.

2 offlineServicing

Nothing required in my example.

3 generalize

amd64_Microsoft-Windows-Security-SPP_6.1.7600.16385_neutral

Set 1 for SkipRearm to allow up to 8 rearms

4 specialize

amd64_Microsoft-Windows-Deployment_6.1.7600.16385_neutral

    RunSynchronous

      RunSynchronousCommand[Order="1"]

        Order: 1
        path: net user administrator /active:yes
        WillReboot: Never

amd64_Microsoft-Windows-Security-SPP-UX_6.1.7600.16385_neutral

SkipAutoActivation: true

amd64_Microsoft-Windows-Shell-Setup_6.1.7600.16385_neutral

Computer Name: Leave blank (we will deal with this at the end)
CopyProfile: true
Registered Organization: Microsoft (you must leave this in this section)
Registered Owner: AutoBVT (you must leave this in this section)
ShowWindowsLive: false
TimeZone: Pacific Standard Time

You can delete other sub-header components if you don’t need them.

5 auditSystem

Nothing required in my example.

6 auditUser

Nothing required in my example.

7 oobeSystem

amd64_Microsoft-Windows-International-Core_6.1.7600.16385_neutral

InputLocale: en-us
SystemLocale: en-us
UILanguage: en-us
UserLocale: en-us

amd64_Microsoft-Windows-Shell-Setup_6.1.7600.16385_neutral

RegisteredOrganization: Your Company Name
RegisteredOwner: Your Name

  • AutoLogon
    1. Enabled: true
      LogonCount: 5
      Username: administrator

        Password: Administrator Password
  • FirstLogonCommands
    1. SynchronousCommand[Order="1"]

        CommandLine: cscript //b c:\windows\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX (windows 7 license key)
        Order 1
        RequiresUserInput: false

      SynchronousCommand[Order="2"]

        CommandLine: cscript //b c:\windows\system32\slmgr.vbs /ato
        Order 2
        RequiresUserInput: false
  • OOBE
    1. HideEULAPage: true
      NetworkLocation: Home
      ProtectYourPC: 1
  • UserAccounts
    1. AdministratorPassword: Administrator Password
      LocalAccounts

        LocalAccount[Name="Administrator"]

          Action: AddListItem
          Description: Local Administrator
          DisplayName: Administrator
          Group: Administrators
          Name: Administrator

            Password: Administrator Password

    If you have questions, look at my image above to see full layout of components, it should help.

    Step #7

    K, now go ahead and save your answer file as sysprep.xml.

    Step #8

    If you want the sysprep to prompt for a computer name you need to remove a line from your XML file. Open up your XML file you saved with notepad and remove the following line:

    Sysprep XML Computer Name

    Sysprep XML Computer Name

    PART 2 – IMAGING PROCESS / RUNNING SYSPREP

    Step #9

    Install Windows 7 (Enterprise) from CD or USB flash drive, when you arrive at the welcome screen and it asks you to create a username, hit ctrl+shift+f3.
    This will reboot your machine and put your windows build in ‘audit’ mode.

    Step #10

    On reboot, you’ll automatically be logged in under the built-in Administrator account. A sysprep GUI box will appear, but you can close it and NOW begin to customize your profile.

    Step #11

    Install any software/drivers, make any profile customizations, etc.
    If you need to reboot, the computer will boot you back into the Administrator account. You will be stuck in this audit mode until you run sysprep with the /oobe parameter. After doing so, sysprep will delete/clean up the Administrator account, but if you have copyprofile=true in your unattended answer file, it will copy the customized Admin account to the default profile before deleting it.

    Step #12

    On the PC you are going to be running sysprep on, you need to create a folder called scripts in this directory: %WINDIR%\Setup\. Now you are going to create a CMD file within the %WINDIR%\Setup\Scripts directory. Right click and make a new text file called SetupComplete.txt. Remove the .txt extension and replace that with .cmd. You now have a SetupComplete.cmd file which windows will read the first time it boots up from the sysprep. We need to place a script inside the CMD file. Edit the cmd file with notepad and insert this line: del /Q /F c:\windows\system32\sysprep\sysprep.xml. This script will delete your sysprep.xml file after it has been used. If you have passwords or cd keys stored in that xml file you don’t have to worry about it being left on the computer.

    Step #13

    Once you have everything configured correctly, Copy or move your sysprep.xml file to : C:\windows\system32\sysprep. Now to run sysprep, navigate to that sysprep folder, hold SHIFT and right click and select “Open New Command Windows Here”. Next, input the following commands:

    sysprep /generalize /oobe /shutdown /unattend:sysprep.xml

    Step #14

    Turn the computer back on and boot to WinPE 3.0 environment (USB stick or CD/DVD). You can use my BrianLeeJackson WinPE3.0 BootLoader to boot up from USB or CD and capture your image. Capture image and save image to network location.
    A Dell 960 or GX755 is a good standard for capturing when you want a generic image for use with multiple systems. Might require injecting additional drivers for 3rd party brands, HP, etc. Most should work though right out of the box.

    Step #15

    On reboot, Windows will run out of the box, as the /oobe is intended. As long as you put your cd key into the sysprep xml file, windows will be activated automatically in the background, you will be automatically logged into the administrator account, and the sysprep.xml file is deleted. You are now ready to use the computer or join it to the domain. Enjoy!

    Share and Enjoy:
    • Twitter
    • Facebook
    • Digg
    • del.icio.us
    • Technorati
    • StumbleUpon
    • Google Bookmarks

    Sysprep Windows 7 – Third Party Anti-Virus

    Friday, November 13th, 2009

    I have run into about 20-30 people over the last couple weeks that were having trouble sysprepping and they all narrowed it down to the same thing; their anti-virus application. It seems that the Sysprep tool is sometimes not working with a lot of the 3rd party anti-virus applications.

    Anti-Virus Applications with Known Issues

    • Norton 2009
    • McAfee
    • AVG
    • Avira
    • ESET NOD32 4.0 (User reported issues)

    Anti-Virus Applications 100% Compatible with Sysprep

    And yes, you probably noticed that both applications are made by Microsoft, go figure. If anyone notices any other anti-virus programs that are causing issues with sysprep please comment on here. Or if you have workaround for these anti-virus apps and sysprep working together please comment.

    Microsoft Security Essentials - Free Alternative

    Microsoft Security Essentials - Free Alternative

    Share and Enjoy:
    • Twitter
    • Facebook
    • Digg
    • del.icio.us
    • Technorati
    • StumbleUpon
    • Google Bookmarks

    Windows 7 Resource Kit – My Blog in a book!

    Wednesday, November 4th, 2009

    I have been blogging a lot over the past year about my experiences with Windows 7, WinPE 3.0, etc. The first reason I started blogging was not only to document for myself but also because I was trying to save others some time. Well, the good news is that Microsoft finally decided to document all these topics. If you haven’t already, drop by Amazon and buy this book:
    Windows® 7 Resource Kit. It is literally my blog in a book with much more detail! Everyone that has asked me questions on this blog, 99% of the answers for them are in this book. It is 1700 pages long, and worth every page. The paperback edition includes a CD in the back with over 250 powershell scripts and an eBook of the entire book.

    Windows 7 Resource Kit

    Windows 7 Resource Kit

    Here is the layout of the book:

    Chapter 1: Overview of Windows 7 Improvements
    Chapter 2: Security in Windows 7
    Chapter 3: Deployment Platform
    Chapter 4: Planning Deployment
    Chapter 5: Testing Application Compatibility
    Chapter 6: Developing Disk Images
    Chapter 7: Migrating User State Data
    Chapter 8: Deploying Applications
    Chapter 9: Preparing Windows PE
    Chapter 10: Configuring Windows Deployment Services
    Chapter 11: Using Volume Activation
    Chapter 12: Deploying with Microsoft Deployment Toolkit
    Chapter 13: Overview of Management Tools
    Chapter 14: Managing the Desktop Environment
    Chapter 15: Managing Users and User Data
    Chapter 16: Managing Disks and File Systems
    Chapter 17: Managing Devices and Services
    Chapter 18: Managing Printing
    Chapter 19: Managing Search
    Chapter 20: Managing Windows Internet Explorer
    Chapter 21: Maintaining Desktop Health
    Chapter 22: Supporting Users with Remote Assistance
    Chapter 23: Managing Software Updates
    Chapter 24: Managing Client Protection
    Chapter 25: Configuring Windows Networking
    Chapter 26: Configuring Windows Firewall and IPsec
    Chapter 27: Connecting Remote Users and Networks
    Chapter 28: Deploying IPv6
    Chapter 29: Configuring Startup and Troubleshooting Startup Issues
    Chapter 30: Troubleshooting Hardware, Driver, and Disk Issues
    Chapter 31: Troubleshooting Network Issues
    Chapter 32: Troubleshooting Stop Messages

    In my opinion this book could be priced a lot higher for all the information it has in it. If you are nerdy enough this would make a great stocking stuffer :)

    Share and Enjoy:
    • Twitter
    • Facebook
    • Digg
    • del.icio.us
    • Technorati
    • StumbleUpon
    • Google Bookmarks

    Run only scripts that you trust. Disable Powershell Message

    Monday, October 26th, 2009

    If you are like me you have probably run into the following error when trying to run powershell scripts. This becomes very annoying and tedious if you are running different scripts on a regular basis.

    “Security Warning – Run only scripts that you trust. While scripts from the Internet can be useful, this script can potentially harm your computer. Do you want to run –.ps1? [D] Do not run [R] Run once [S] Suspend [?] Help (default is “D”):

    Step #1

    The first thing you need to do is launch Windows Powershell.

    Step #2

    Then enter the following commands:

    get-executionpolicy

    set-executionpolicy bypass

    Powershell Trust Scripts

    Powershell Trust Scripts

    Now launch your script and enjoy not seeing that annoying message come up.

    Share and Enjoy:
    • Twitter
    • Facebook
    • Digg
    • del.icio.us
    • Technorati
    • StumbleUpon
    • Google Bookmarks

    Completely removing Windows Vista/Windows 7 Printer Driver

    Sunday, October 25th, 2009

    If you right click on a printer and delete it, this doesn’t remove the printer driver from the machine. Sometimes when working with print servers and testing multiple drivers there will be times when you need to completely remove a driver package from the machine so you can install a new or different one.

    Windows Vista and Windows 7 has a tool called the Microsoft Management Console (MMC) built into windows which you will use to remove the drivers.

    Step #1

    Reboot the machine and login as “Administrator”.

    Step #2

    Go to the start menu and start typing MMC, you will see the Microsoft Management Console shortcut appear in the start menu; click on it.

    MMC - Remove Print Driver

    MMC - Remove Print Driver


    MMC

    MMC

    Step #3

    Go up to the file menu and select Add/Remove Snap-in…

    MMC - Add/Remove Snap-in...

    MMC - Add/Remove Snap-in...

    Step #4

    Then scroll down in the list and select the “Print Management” snap-in and then hit “Add”.

    MMC - Print Management

    MMC - Print Management

    Step #5

    At this screen you are going to want to select “Add the Local Server”, hit Finish, and then hit ok.

    MMC - Add the Local Server

    MMC - Add the Local Server

    Step #6

    Then you can scroll down to your computer name, select the drivers tree and then right click on the driver you want to remove and select “Remove Driver Package”.

    MMC - Remove Driver Package

    MMC - Remove Driver Package

    Step #7

    Make sure you reboot your machine before trying to add new or different print drivers.

    Share and Enjoy:
    • Twitter
    • Facebook
    • Digg
    • del.icio.us
    • Technorati
    • StumbleUpon
    • Google Bookmarks

    VCSY Updates – Microsoft and Windows 7

    Wednesday, October 21st, 2009

    This timeline has been presented by a few bloggers already; but here it is again for those who might have just started following VCSY:

  • Microsoft RELEASE of Windows 7 Oct. 22nd (RIGHT NOW!!)
  • Microsoft 1st Quarter report due about October 23rd
  • Microsoft’s $2 Billion credit facility expires November 6′ 2009
  • NAVPath set to be launched at the 2009 Directions Conference November 11-14th
  • VCSY’s 10Q report -Nov. 14th (Partnership?)
  • Azure is expected to unveil at the 2009 PDC November 16-19th
  • Microsoft’s $1 Billion 364-credit facility expires March 12′ 2010
  • What we can hope for is that Microsoft mention’s VCSY in press conference and then things will really skyrocket. Also, Windows 7 has already become Amazon’s biggest pre-order to date; outselling Harry Potter.

    Share and Enjoy:
    • Twitter
    • Facebook
    • Digg
    • del.icio.us
    • Technorati
    • StumbleUpon
    • Google Bookmarks

    Ping returns IPv6 Address, ping IPv4?

    Tuesday, October 6th, 2009

    If you are on the same network, or Vlan, or subnet as someone else you will probably notice that if you ping their hostname it will return with a IPv6 address.

    If you want to still see what their IPv4 address is then simply use the command below:

    ping hostname -4

    Simply add a “-4″ after your normal ping command.

    Share and Enjoy:
    • Twitter
    • Facebook
    • Digg
    • del.icio.us
    • Technorati
    • StumbleUpon
    • Google Bookmarks

    UVNC SC working slow in Windows 7 Environment

    Saturday, September 26th, 2009

    Some of you may have noticed the UVNC SC working slow between windows 7 machines. To fix this, you simply need to recompile your HelpDesk.exe and download the latest version of UVNC client.

    Rudi De Vos over in the UltraVNC forums posted a fix for this problem.

    Also, here is the link for the newest version of UVNC.

    I have tested Rudi’s fix in test environment and we are now using this in production environment within Windows 7 environment and it is working great. Thanks Rudi!

    UVNC Listener

    UVNC Listener

    Share and Enjoy:
    • Twitter
    • Facebook
    • Digg
    • del.icio.us
    • Technorati
    • StumbleUpon
    • Google Bookmarks

    Sysprep a Windows 7 Machine – Start to Finish

    Tuesday, September 8th, 2009

    THIS IS OLD, PLEASE SEE NEW VERSION 2, CLICK HERE

    This is a step by step guide on Sysprepping (and yes, I have made sysprepping a verb now) a Windows 7 machine from start to finish. This will guide you through building the unattended XML file, having the administrator profile copy over to default profile, and fixes for what is right now a not 100% working system from Microsoft. This is something I would have easily paid for when first starting this process. I don’t know why Microsoft can’t hand us a 100% working process. There will always be fixes, even with the RTM release.

    Here is a list of what you will need:

    - Latest version of WAIK : KB3AIK_EN.iso Version 1.0
    - Windows Vista or Windows 7 Machine to build the XML file on
    - ISO or DVD of Windows 7 Installation (x32 or x64)
    - WinPE Boot Environment : BrianLeeJackson WinPE 3.0 BootLoader

    Once you have WAIK installed on a machine your Start Menu should look like the image below:

    Windows 7 WAIK Version 1

    Windows 7 WAIK Version 1

    Go ahead and launch the Windows System Image Manager. Picture of the program is below.

    Windows System Image Manager

    Windows System Image Manager

    We now need to open a Windows 7 image. If you have an installation DVD, insert it now. Or if you have an ISO of 7, go ahead and extract it to a folder on your desktop. (I recommend 7-zip). Back in Windows System Image Manager (WISM) go to the file menu and select “Select Windows Image”. You will now want to browse to the .CLG file in your Windows 7 installation (I am using Windows 7 Enterprise x64 in my example). It is located in the sources folder. See Image below.

    Selecting CLG File - WSIM

    Selecting CLG File - WSIM

    Now we need to create a new answer file. Go to the file menu and select “Create New Answer File.” Right after creating one, go ahead and simply go to file menu and select “Save Answer File.” This will give your XML file a name and save location. Now you see we have two category folders, Components and Packages. Under the Components folder you see that we have 7 options:

    - 1 windowsPE
    - 2 offlineServicing
    - 3 generalize
    - 4 specialize
    - 5 auditSystem
    - 6 auditUser
    - 7 oobeSystem

    These are very important as these are the steps in which the XML file is sequenced.

    The next part is a little confusing. You are going to add components, from under the “Windows Image” section on the bottom left hand side to the passes on your Answer File. To add a component, you can right click on them and select “add to # pass”. There are many different options you can add, but they have to be done in a certain order and pass otherwise your sysprep might fail. I am simply going to use the one I created as the example.

    Download my Windows 7 x86 Sysprep XML File
    Download my Windows 7 x64 Sysprep XML File

    WSIM Passes

    WSIM Passes

    Here is more information about adding options under the passes:

    1 WindowsPE

    Nothing required in my example.

    2 OfflineServicing

    Nothing required in my example.

    3 Generalize

    amd64_Microsoft-Windows-Security-SPP_neutral

    Set 1 for SkipRearm to allow up to 8 rearms

    4 Specialize

    amd64_Microsoft-Windows-Security-SPP-UX_neutral

    SkipAutoActivation: true

    amd64_Microsoft-Windows-Shell-Setup_neutral

    Computer Name: * (Randomly generated name, use this to test)
    CopyProfile: false (doesn’t quite work, we will do that manually later)
    Registered Organization: Microsoft (you must leave this in this section)
    Registered Owner: AutoBVT (you must leave this in this section)
    ShowWindowsLive: false
    TimeZone: Pacific Standard Time

    5 AuditSystem

    Nothing required in my example.

    6 AuditUser

    Nothing required in my example.

    7 OobeSystem

    amd64_Microsoft-Windows-International-Core_neutral

    InputLocale: en-us
    SystemLocale: en-us
    UILanguage: en-us
    UserLocale: en-us

    amd64_Microsoft-Windows-Shell-Setup_neutral

    RegisteredOrganization: YourCompanyName
    RegisteredOwner: YourName

    Under amd64_Microsoft-Windows-Shell-Setup_neutral component, you will have a subheader for OOBE:

    HideEULAPage true
    NetworkLocation: Home
    ProtectYourPC: 1

    Under amd64_Microsoft-Windows-Shell-Setup_neutral component, you will have a subheader for UserAccounts:

    You will want to add both an administrator password and another local account with administrator rights and password.

    If you have questions, look at my image above to see full layout of components, it should help. Also, you might have additional component headings that I didn’t mention. If you are simply testing first time, just delete them for now. You can add all sorts of components later on, you should do a successful sysprep if this is your first time, better to keep it simple and to the basics.

    K, now go ahead and save your answer file. The building of the XML file is now done. That is the worst part. You would think that the sysprep process would get easier as new OS’s come out, but its pretty much the exact opposite.

    Prepping your machine

    K, now it is time to get your machine that you want to sysprep and capture an image of ready to go. First, you are going enable the administrator account on the computer. To do this on Windows Vista or Windows 7, open up a command prompt (Run as Administrator) and input the following command:

    net user administrator /active:yes

    Hit enter and you should see “successfully enabled Administrator Account”.

    So you should currently have two accounts on your computer. The account you are currently logged into and the Administrator account which you just enabled. You are going to want to customize all of your preferences, favorites, bookmarks, taskbar, etc. under the currently logged in account. Once you have everything just perfect, you are going to reboot the computer and login to the administrator account. This next part is very important. You are going to go to “My Computer” and then to Organize and folder and search options. Go ahead and select “Show hidden files, folders, and drives”. Picture is below.

    Show Hidden Files, Folders, and Drives

    Show Hidden Files, Folders, and Drives


    No go to “My Computer” and you are going to rename the Default folder to Default.bak (The CopyProfile setting in Sysprep on Windows7 does not seem to work yet). Next, copy your other user account, the one you customized everything in, right click on it and select copy. Then paste within that same window. It is going to come out as USERNAME – COPY. Now rename this copied folder to Default. Now after you sysprep your computer it will create all new accounts from that default profile folder using all your customized options.

    The last thing we need to do is disable the WMP sharing service. This is a bug in Windows 7 and hopefully will eventually be fixed. If you don’t disable this before the sysprep your sysprep will simply fail to run. Go to run, msconfig, and then disable the “Windows Media Player Networking Sharing” service.

    Now you are ready to sysprep your computer and capture an image of it!! Finally! So, grab that XML file you created earlier and you are going to place it on the machine you built your image on. Copy or move it to : C:\windows\system32\sysprep.

    Now to run sysprep, navigate to that sysprep folder, hold SHIFT and right click and select “Open New Command Windows Here”.
    Next, input the following commands:

    sysprep /generalize /oobe /shutdown /unattend:NAMEOFYOURANSWERFILE.xml

    Your computer will now run the sysprep process, removing SID, etc, and then shutdown. You can have it restart, but shutdown is always safer if you have a ton of things going on. You will need to boot to your WinPE Boot environment when your computer starts back up. If you miss the first time upon boot up, you will have to re-input your sysprep commands. So do a shutdown, not a restart.

    You can use my BrianLeeJackson WinPE3.0 BootLoader to boot up from USB or CD and capture your image. Once you capture your image, you are all done. You now have a sysprepped Windows 7 image. I have performed this task on over 120 computers so far and it has been flawless. The hard part was getting everything configured correctly. I hope this documentation helps someone out there, I know I would have killed for a tutorial like this when I first started :)

    Share and Enjoy:
    • Twitter
    • Facebook
    • Digg
    • del.icio.us
    • Technorati
    • StumbleUpon
    • Google Bookmarks

    How to install HP Mini TouchPad drivers

    Saturday, September 5th, 2009

    If anyone has recently purchased an HP Mini Netbook they might notice one thing not working after a fresh install of Windows 7. The touchpad scrolling doesn’t seem to work after fresh install of Windows 7 x32. Read below to find out what you need to get it working. The nice thing is, Windows Updates should pick up everything else automatically.

    HP Mini Netbook

    HP Mini Netbook

    Step #1

    First thing you will need to do is download the Synaptics Touchpad Driver from their website. Download them here.

    Step #2

    If this is a netbook, most likely you are running 32-bit of Windows 7 and so you will need to click on “Windows Vista 32-bit Edition v10.1.8″ while on Synaptics’ website.

    Step #3

    Once you download it, simply double click on it to run it and then you will have to restart your computer.

    Step #4

    No configuration is necessary. Once you have restarted, you will once again have your touchpad scrolling back.

    Share and Enjoy:
    • Twitter
    • Facebook
    • Digg
    • del.icio.us
    • Technorati
    • StumbleUpon
    • Google Bookmarks