Based on the current progress for Windows 10 version 1903, due to arrive next spring, it now looks like the fall update for the OS will arrive around Sept. 10 or Sept. 24.

Microsoft last week released the first preview of what will become Windows 10 version 1903, the opening feature upgrade of next year, slated to ship in the spring.

The debut of what Microsoft calls the “Skip Ahead” build for Windows 10 1903 also hints that the release of this fall’s upgrade, aka 1809, will take place in September. If so, it would be the first time since late-2015 that the actual delivery date matched the numerical label.

On July 25, Microsoft forked the 1809 preview of Windows 10 – as it’s done before when a feature upgrade approaches – so developers could continue to deliver betas for that build while also beginning to work on the next-in-line, 1903. (Microsoft uses a yymm labeling system to mark its Windows 10 feature upgrades; 1809 should indicate a September 2018 release, while 1903 would be a March 2019 release.)

When it forks preview code, Microsoft provides the even-further-in-the-future build, in this case, 1903, to Windows Insider participants who earlier volunteered for Skip Ahead. As the current feature upgrade gets close to release, Microsoft switches Skip Ahead users to the following upgrade, so that engineers can start collecting feedback on that version even as they keep polishing the one set to launch soon. The bulk of Insiders remain on the latter.

Think of the Skip Ahead debut as a warning bell, like the one rung at track meets when racers start the final lap: When Microsoft begins to ship Skip Ahead code, it’s close to wrapping up the impending feature upgrade.

In 2017, as Windows 10 1709 (aka “Fall Creators Update”) neared completion, Microsoft first forked the preview code and distributed a different build to Skip Aheaders on Aug. 31. Windows 10 1709 began its release cycle on Oct. 17, or 47 days later. With this year’s version 1803, Skip Ahead debuted Feb. 14, or 75 days before the April 30 release of that upgrade.

(Windows 10 1803’s original launch date, reportedly April 10 – which was one of two dates Computerworld had forecast in February – was postponed by 20 days after a deal-breaking bug was uncovered at nearly the last minute.)

For one estimate of the release date for Windows 10 1809, Computerworld added 47 days to July 25, arriving at Sept. 10. A second estimate was generated by adding 61 days – the average of the two previous Skip Ahead triggers – to July 25, resulting in a Sept. 24 rollout.

Because the last three feature upgrades launched on either a Monday or Tuesday – April 11, 2017 for version 1703; Oct. 17, 2017 for 1709; April 30, 2018 for 1803 – Sept. 10 or 11 would be the most likely release dates for 1809, absent a show-stopping problem like the bug before 1803’s launch. Computerworld’s alternate forecast would be September 24 or 25, also a Monday/Tuesday combination, because it would match the previous upgrades’ average time-between-Skip-Ahead-and-release.

If Microsoft does release Windows 10 1809 in September, it would be the first time since November 2015 that the company has matched delivery date and the upgrade’s label. Version 1511 debuted Nov. 10, 2015. The four subsequent upgrades, 1607, 1703, 1709 and 1803, all missed their release months by between 2 and 30 days. (Version 1607 came the nearest, releasing Aug. 2, 2016.)

Although Microsoft has never expressly tied itself to March and September release months – in a support document, it gives itself wiggle room by stating that feature upgrades will be released “twice per year, around March and September [emphasis added]” – the disconnect between release and numerical designation has always seemed odd.

Issuing feature upgrades during the appointed months would be a sign that Microsoft has gotten a better handle on the rapid development tempo it has at times struggled with executing. It would also be a step toward a more predictable schedule, which was the point of the pledge it made over a year ago to issue a pair of feature upgrades annually.

After performing an in-place upgrade on a Windows machine, you will find a WINDOWS.OLD folder in the root of C:. This folder will have a backup of your old program files, appdata and Windows folder… just in case you need to revert back or recover something that might have been lost during the upgrade. When you try to delete it though you are told you don’t have permissions. Just a small point here, it is generally not recommended to do in-place upgrades on servers. In fact there are some products (e.g. Exchange, ConfigMgr) that explicitly state they do not support upgrading the Operating System. There is of course a difference between “what works” and “what is supported”, but we do suggest where possible you do a clean Server install and migrate your application to the new server. Anyway, let’s assume you’ve understand all the risks and have done a successful in-place upgrade, you now find the old WINDOWS.OLD folder of several GB in size sitting there. If all is well, then you might as well just delete it.

SOLUTION

On Desktop OS version, you can just use the disk cleanup tool to remove it, but that is not available (by default) on Servers, so there are a couple of approaches.

Command line tools to take ownership and delete the folder. Make sure to “run as administrator”

How can I delete the windows.old from an upgraded Windows Server?

For a client OS that’s upgraded, the Disk Cleanup utility can be used to delete the very large windows.old folder containing the old OS. This isn’t available on a server OS without installing the Desktop Experience feature.

To delete, it is necessary to take ownership of the folder, give administrators full control, then delete. This can be done with the commands below:

•  takeown /F c:\Windows.old\* /R /A /D Y
•  cacls c:\Windows.old\*.* /T /grant administrators:F
•  rmdir /S /Q c:\Windows.old

Or you can add the “Desktop” features to provide the Disk Cleanup tool:

Step By Step Guide to Enabling “Disk Cleanup Utility”

1. Open The Roles and Features Wizard

To open the roes and feauture wizard. Lauch the “server manager” by pressing the Windows key

and clicking on the server manage please see Screenshot as shown.

Personally, the command line option is less messy and saves having to add features to your server that don’t really need to be there.

2. Click on Add role and Feature

Click on add role and feture to launch the add role and feature wizard.

3.  Choose installation Type

Choose rolebase or feature based installation to install to local machine.

4. Click Next all the way to features

Click “next” all the way to features. Locate “User Interface and Infrastructure”. Click on “Desktop Experience”

and install additional required feature.

5.  Proceed with the installation and Reboot

Make it sure that you reboot the system

6.  Verify that the Utility is indeed installed

Ready to run diskcleanup. See screen shot below.

Disk Cleanup in Action

Below is a sample snapshot of disk cleanup in action.

If you’re one of the many business users who has not upgraded their computer to Windows 10, there are still resources to boost your experience. Here are 10 tips for getting the most out of the OS.

Windows 10 faced a controversial roll-out, with privacy concerns, bugs, and other issues plaguing many users. And as of August 2016, just 1% of business machines had upgraded to Windows 10, according to a study from Softchoice. Instead, 91% of the machines were operating with Windows 7—an 18% increase over the same period of time in 2015.

“It seems businesses don’t see an urgent need to move operating systems, so long as their cloud-based applications are still running fine on Windows 7,” Softchoice’s Microsoft director Craig McQueen wrote in a press release at the time. “In addition to the security benefits, I think once organizations grasp the user benefits—such as touch and Cortana—we will start to see a boost in adoption.”

While experts predict Windows 10 deployments will pick up this year, it’s important for those still using Windows 7 for business to get the most out of their machines. Here are 10  articles with Windows 7 tips that will help enterprise users operate the machines more effectively.

1. 10 ways to speed up Windows 7

While Windows 7 generally performs well, over time, the system can slow down and require some care to get it back up to speed. The OS also contains certain features that users can take advantage of to improve overall performance. Here, we outline 10 steps business users can take to enhance the performance of your Windows 7 system.

2. Use multiple monitors with Windows 7’s Remote Desktop Connection

Windows 7 allows users to connect to a remote computer and utilize the local system’s multiple monitors. Here is a step by step advice on how to configure and operate multiple monitors using Windows 7’s Remote Desktop Connection, as well as how to connect to and from Windows versions that do not support this feature.

3. Quick Tips: Flush the ARP cache in Windows 7

The Address Resolution Protocol (ARP) cache is an important part of IP networking on any OS, as it links Ethernet addressing to hardware addressing. Newly mapped addresses are saved in an ARP cache, which is usually fine, but can sometimes cause issues with internet connections and web page loading times. Here, are the necessary steps to clear the ARP cache, and how to manage it going forward.

4. 10+ Windows 7 services you may not need

While every version of Windows includes a core set of system services, business users can disable some that are not necessary in order to improve performance and security. In this article, we highlight 13 services that users can disable if they so choose on Windows 7 systems that will likely not have any impact on business operations, including IP Helper, offline files, and Network Access Protection.

5. 10 Windows 7 commands every administrator should know

IT staff who troubleshoot Windows 7 problems often have to dive into the command line. Here, are 10 fundamental Windows 7 commands that are useful for IT administrators, including System File Checker, File Signature Verification, and Driverquery.

6. Modifying the Windows 7 boot loader with the Boot Configuration Data Editor tool

In Windows Vista and later versions of Windows, the bootloader was moved from boot.ini to a utility called BCDEdit. This article walks users through how to modify the boot config data using this tool.

7. Change and customize Windows 7’s Logon screen wallpaper

Changing and customizing the Windows 7 Logon screen wallpaper is easy once you know the steps, as Microsoft built the ability to change the wallpaper right into the OS, as opposed to needing any third-party software. Here, we offer a tutorial on doing so.

8. Change the Processor Affinity setting in Windows 7 to gain a performance edge

Most applications have been designed for multi-core processors, and work with an OS to distribute their operations evenly across cores to enhance performance. However, you can sometimes achieve better overall performance from certain applications by configuring them to run on different processor cores, which Windows 7 allows via the Processor Affinity setting. In this article, we explain two ways to change the Processor Affinity setting in Windows 7.

9. Use Windows 7 Event Viewer to track down issues that cause slower boot times

Experiencing a slow Windows 7 boot time? You can use Windows 7’s Event View to investigate the source of the problem. The Event Viewer includes a category of event logs called Applications and Services Logs, which track key elements of the OS. Here, we explain how it is possible to find out how long it took to boot up your system every time, since the day Windows 7 was first installed, along with instances where boot time slowed down, all through these logs.

10. Tag your files for easier searches in Windows 7

This article, walks users through how to tag files to make them searchable via the Search filters built into Windows Explorer’s Search box in Windows 7. It’s possible to do this easily from many applications while saving a file. The ability to more easily find files is a boon for business users who want to enhance their productivity.

Have questions?

Get answers from Microsofts Cloud Solutions Partner!
Call us at: 856-745-9990 or visit: https://southjerseytechies.net/

South Jersey Techies, LL C is a full Managed Web and Technology Services Company providing IT Services, Website Design Services, Server Support, Network Consulting, Internet Phones, Cloud Solutions Provider and much more. Contact for More Information.

To read this article in its entirety click here.

Under specific circumstances and with careful tweaking, you can increase Windows 7’s performance using the Processor Affinity setting.

If you have a multi-core processor, chances are good that on the Performance tab in Windows Task Manager, you have noticed that the CPU Usage History graphs look about the same for each core, as shown in Figure A. The reason for this is that most applications you run these days have been designed with multi-core processors in mind and will work with the operating system to distribute their operations as evenly as possible across all the available cores.

Figure A

In most cases, you’ll notice that the CPU Usage History graphs look about the same for each core.

In most cases this even distribution provides you with the best performance possible. However, that’s not always going to be the case. For instance, older applications that were designed for single-core processors can behave irrationally — they may all of a sudden begin maxing out the CPU usage at 100 percent and appear to be locked up. In other circumstances, you might be able to achieve better overall performance from certain applications by configuring each of them to run on different processor cores.

Fortunately, Windows 7 allows you to configure applications to use only one, or several, of the processor cores in a multi-core system by using the Processor Affinity setting.

In this edition of the Windows Desktop Report, Iwe’ll show you two ways to change the Processor Affinity setting in Windows 7.

From Task Manager

Changing the Processor Affinity setting from within Task Manager is a pretty straightforward operation once you know how to do it. To launch Task Manger, you can use the keystroke combination [Ctrl] + [Shift] + [Esc] or you can simply right-click on the taskbar and select Task Manager from the context menu.

Once Task Manager is up and running, select the Applications tab, right-click on the application that you want to work with, and select the Go to Process command, as shown in Figure B. When you get to the Processes tab, right-click on the process and from that context menu, select the Set Affinity command, as shown in Figure C. (If the processes are jumping around, it may be hard to select the correct process, so you might just want to press the Application key or [Shift]+[F10].)

Figure B

Right-click on an application and select the Go to Process command.

Figure C

Right-click on the process and select the Set Affinity command.

After you select the Set Affinity command, you’ll see the Processor Affinity dialog box shown in Figure D. As you can see, the default setting is All Processors, which in the case of my example system are CPU 0 and CPU 1. At this point, you can clear the All Processors check box and then select the CPU on which you want the process to run.

Figure D

The Processor Affinity dialog box allows you to choose which processor(s) you want to use.

An example

To take a look at the effects of using the Set Affinity command, we launched two applications: Microsoft Security Essentials and Disk Defragmenter. Next we used the Set Affinity command to assign Microsoft Security Essentials to CPU 0 and Disk Defragmenter to CPU 1. We then started each application running — Microsoft Security Essentials performing a full scan and Disk Defragmenter defragging a 500GB disk.

Once each application began working, they started sucking up CPU time, so we went to the Performance tab in Windows Task Manager to look at the CPU Usage History graphs. When we did, we could see that each graph was showing different measurements, as shown in Figure E.

Figure E

Each of the CPU Usage History graphs shows different measurements.

To specifically see how each CPU core was faring, we launched Resource Monitor and selected the CPU tab. Again, we could see that each CPU core was showing different usage measurements, as shown in Figure F.

Figure F

Resource Monitor’s CPU tab specifically identifies each CPU core and its usage.

Now, of course, my example combination is purely for the sake of showing each CPU handling a separate process. However, there are instances where running Microsoft Security Essentials on a separate CPU core would be beneficial.

From a shortcut

Now if you find that running an application on a specific CPU core works well, you might want to use it again in the future. If so, chances are that you won’t want to have to go through the Task Manager each time. Fortunately you can create a shortcut to launch an application with a specific affinity setting.

For example, to launch Disk Defragmenter so that it runs only on CPU 0, you would create a shortcut with the following command line:

C:\Windows\System32\cmd.exe /C start /affinity 1 dfrgui.exe

To launch Disk Defragmenter on CPU 1, you would create a shortcut with the following command line:

C:\Windows\System32\cmd.exe /C start /affinity 2 dfrgui.exe

The number that follows the start /affinity command is called the affinity mask and is defined as a hexadecimal number. However, the CPU core number can be calculated more easily using binary numbers. For instance, the command

C:\Windows\System32\cmd.exe /C start /affinity 3 dfrgui.exe

will launch Disk Defragmenter on both CPU 0 and CPU 1. If you convert 3 into a binary number you will get 0011. Under the affinity mask system, processors are numbered from the right to left beginning with 0 and since there are 1’s in the first two places, this indicates CPU 0 and CPU 1.

Suppose you have a Quad core processor. If so and you use an affinity mask of 4, that will convert into binary 0100, which indicates CPU 2. If you use an affinity mask of 9, that will convert into binary 1001, which indicates CPU 0 and CPU 3.

For more information on the start /affinity command, open a Command Prompt window and type the command

start /?

Have questions?

Get answers from Microsofts Cloud Solutions Partner!
Call us at: 856-745-9990 or visit: https://southjerseytechies.net/

South Jersey Techies, LL C is a full Managed Web and Technology Services Company providing IT Services, Website Design Services, Server Support, Network Consulting, Internet Phones, Cloud Solutions Provider and much more. Contact for More Information.

To read this article in its entirety click here.

The command line is often the best place to resolve Windows 7 desktop problems. These basic commands will help speed your troubleshooting tasks.

PC troubleshooting is becoming less common in larger organizations, but consultants and techs in smaller shops still have to get their hands dirty identifying and fixing desktop problems. Oftentimes, troubleshooting Windows 7 means delving into the command line. Here are 10 fundamental Windows 7 commands you might find helpful.

1: System File Checker

Malicious software will often attempt to replace core system files with modified versions in an effort to take control of the system. The System File Checker can be used to verify the integrity of the Windows system files. If any of the files are found to be missing or corrupt, they will be replaced. You can run the System File Checker by using this command:

sfc /scannow

2: File Signature Verification

One way to verify the integrity of a system is to make sure that all the system files are digitally signed. You can accomplish this with the File Signature Verification tool. This tool is launched from the command line but uses a GUI interface. It will tell you which system files are signed and which aren’t. As a rule, all the system files should be digitally signed, although some hardware vendors don’t sign driver files. The command used to launch the File Signature Verification tool is:

sigverif

3: Driverquery

Incorrect device drivers can lead to any number of system problems. If you want to see which drivers are installed on a Windows 7 system, you can do so by running the driverquery tool. This simple command-line tool provides information about each driver that is being used. The command is:

driverquery

If you need a bit more information, you can append the -v switch. Another option is to append the -si switch, which causes the tool to display signature information for the drivers. Here’s how they look:

driverquery -v

driverquery -si

4: Nslookup

The nslookup tool can help you to verify that DNS name resolution is working correctly. When you run nslookup against a host name, the tool will show you how the name was resolved, as well as which DNS server was used during the lookup. This tool can be extremely helpful when troubleshooting problems related to legacy DNS records that still exist but that are no longer correct.

To use this tool, just enter the nslookup command, followed by the name of the host you want to resolve. For example:

nslookup dc1.contoso.com

5: Ping

Ping is probably the simplest of all diagnostic commands. It’s used to verify basic TCP/IP connectivity to a network host. To use it, simply enter the command, followed by the name or IP address of the host you want to test. For example:

ping 192.168.1.1

Keep in mind that this command will work only if Internet Control Message Protocol (ICMP) traffic is allowed to pass between the two machines. If at any point a firewall is blocking ICMP traffic, the ping will fail.

6: Pathping

Ping does a good job of telling you whether two machines can communicate with one another over TCP/IP, but if a ping does fail, you won’t receive any information regarding the nature of the failure. This is where the pathping utility comes in.

Pathping is designed for environments in which one or more routers exist between hosts. It sends a series of packets to each router that’s in the path to the destination host in an effort to determine whether the router is performing slowly or dropping packets. At its simplest, the syntax for pathping is identical to that of the ping command (although there are some optional switches you can use). The command looks like this:

pathping 192.168.1.1

7: Ipconfig

The ipconfig command is used to view or modify a computer’s IP addresses. For example, if you wanted to view a Windows 7 system’s full IP configuration, you could use the following command:

ipconfig /all

Assuming that the system has acquired its IP address from a DHCP server, you can use the ipconfig command to release and then renew the IP address. Doing so involves using the following commands:

ipconfig /release

ipconfig /renew

Another handy thing you can do with ipconfig is flush the DNS resolver cache. This can be helpful when a system is resolving DNS addresses incorrectly. You can flush the DNS cache by using this command:

ipconfig /flushdns

8: Repair-bde

If a drive that is encrypted with BitLocker has problems, you can sometimes recover the data using a utility called repair-bde. To use this command, you will need a destination drive to which the recovered data can be written, as well as your BitLocker recovery key or recovery password. The basic syntax for this command is:

repair-bde <source> <destination> -rk | rp <source>

You must specify the source drive, the destination drive, and either the rk (recovery key) or the rp (recovery password) switch, along with the path to the recovery key or the recovery password. Here are two examples of how to use this utility:

repair-bde c: d: -rk e:\recovery.bek

repair-bde c: d: -rp 111111-111111-111111-111111-111111-111111

9: Tasklist

The tasklist command is designed to provide information about the tasks that are running on a Windows 7 system. At its most basic, you can enter the following command:

tasklist

The tasklist command has numerous optional switches, but there are a couple I want to mention. One is the -m switch, which causes tasklist to display all the DLL modules associated with a task. The other is the -svc switch, which lists the services that support each task. Here’s how they look:

tasklist -m

tasklist -svc

10: Taskkill

The taskkill command terminates a task, either by name (which is referred to as the image name) or by process ID. The syntax for this command is simple. You must follow the taskkill command with -pid (process ID) or -im (image name) and the name or process ID of the task that you want to terminate. Here are two examples of how this command works:

taskkill -pid 4104

taskkill -im iexplore.exe

Have questions?

Get answers from Microsofts Cloud Solutions Partner!
Call us at: 856-745-9990 or visit: https://southjerseytechies.net/

South Jersey Techies, LL C is a full Managed Web and Technology Services Company providing IT Services, Website Design Services, Server Support, Network Consulting, Internet Phones, Cloud Solutions Provider and much more. Contact for More Information.

To read this article in its entirety click here.

If you evaluate your organization’s need for certain Windows 7 services, you may find that a number of them can be safely disabled.

Every version of Windows has shipped with a core set of system services that must run so that the system can perform basic operations. However, your organization may not necessarily need to have all the services running, and disabling unnecessary services can enhance performance and security. We’ve put together a list of 13 services you can disable on your Windows 7 systems that will probably not negatively affect your business operations at all.

Before you take drastic action, such as disabling a service on every PC in your organization, make sure that the service you’re disabling is not actually in use. This article makes a couple of broad assumptions: that your company doesn’t need to share Windows Media files and doesn’t use Windows 7’s HomeGroup features.

This is not a definitive list of services that can be disabled; these are just some obvious ones. Read carefully and make sure you test changes before deploying them across your organization.

1: IP Helper

Windows description: Provides tunnel connectivity using IPv6 transition technologies (6to4, ISATAP, Port Proxy, and Teredo) and IP-HTTPS. If this service is stopped, the computer will not have the enhanced connectivity benefits that these technologies offer. Why this can be disabled:Many organizations haven’t even started testing IPv6, much less fully deployed it. As indicated in the service description, the IP Helper service is leveraged in IPv4-to-IPv6 transitions.

2: Offline Files

Windows description: The Offline Files service performs maintenance activities on the Offline Files cache, responds to user logon and logoff events, implements the internals of the public API, and dispatches interesting events to those interested in Offline Files activities and changes in cache state. Why this can be disabled: If your organization doesn’t use the Offline Files feature found in both Windows client and server products, this service can be safely disabled. Obviously, if you are synchronizing files across the network, you shouldn’t disable this service.

3: Network Access Protection Agent

Windows description: The Network Access Protection (NAP) agent service collects and manages health information for client computers on a network. Information collected by the NAP agent is used to make sure that the client computer has the required software and settings. If a client computer is not compliant with health policy, it can be provided with restricted network access until its configuration is updated. Depending on the configuration of health policy, client computers might be automatically updated so that users quickly regain full network access without having to manually update their computer. Why this can be disabled: If you’re not doing network-based remediation or if you’re doing remediation with a third-party tool that doesn’t leverage the NAP client, this service can be disabled.

4: Parental Controls

Windows description: This service is a stub for Windows Parental Control functionality that existed in Vista. It is provided for backward compatibility only. Why this can be disabled:Corporate networks rarely used Vista’s Parental Control functionality. Further, this is a legacy service from Windows Vista.

5: Smart Card

Windows description: Manages access to smart cards read by this computer. If this service is stopped, this computer will be unable to read smart cards. If this service is disabled, any services that explicitly depend on it will fail to start. Why this can be disabled: If your organization does not use smart cards for authentication purposes, you can safely disable this service.

6: Smart Card Removal Policy

Windows description: Allows the system to be configured to lock the user desktop upon smart card removal. Why this can be disabled: If your organization does not use smart cards for authentication purposes, you can safely disable this service.

7: Windows Media Center Receiver Service

Windows description: Windows Media Center Service for TV and FM broadcast reception. Why this can be disabled: In most corporate environments, TV and FM broadcast reception on desktop computers is not considered a “business critical” item that needs support, and it’s often not allowed anyway. You can disable this service to save some resources.

8: Windows Media Center Scheduler Service

Windows description: Starts and stops recording of TV programs within Windows Media Center.Why this can be disabled: Likewise, there’s no need to record TV programs in a corporate environment.

9: Windows Media Player Network Sharing Service

Windows description: Shares Windows Media Player libraries to other networked players and media devices using Universal Plug and Play. Why this can be disabled: On a corporate network, Windows Media Player doesn’t have nearly the place it might have on a home network. Disabling this service will have no impact on business activities.

10: Fax

Windows description: Enables you to send and receive faxes, utilizing fax resources available on this computer or on the network. Why this can be disabled: If your organization is not using a network-based faxing service, disabling this service will have no business impact.

11: HomeGroup Listener

Windows description: Makes local computer changes associated with configuration and maintenance of the homegroup-joined computer. If this service is stopped or disabled, your computer will not work properly in a homegroup and your homegroup might not work properly. It is recommended that you keep this service running. Why this can be disabled: It’s highly unlikely that a business organization — except a very small one — is using HomeGroups as a way to share resources on a network. It’s almost always safe to disable this service in a business setting.

12: HomeGroup Provider

Windows description: Performs networking tasks associated with configuration and maintenance of homegroups. If this service is stopped or disabled, your computer will be unable to detect other homegroups and your homegroup might not work properly. It is recommended that you keep this service running. Why this can be disabled: As noted above: Only very small organizations are likely to use HomeGroups to share resources on a network, so it’s almost always safe to disable this service in a business setting.

13: Tablet PC Input Service

Windows description: Enables Tablet PC pen and ink functionality. Why this can be disabled: The vast majority of PCs that are deployed to users do not have hardware that can leverage tablet-like capability. This service simply uses system resources with no possible benefit.

Have questions?

Get answers from Microsofts Cloud Solutions Partner!
Call us at: 856-745-9990 or visit: https://southjerseytechies.net/

South Jersey Techies, LL C is a full Managed Web and Technology Services Company providing IT Services, Website Design Services, Server Support, Network Consulting, Internet Phones, Cloud Solutions Provider and much more. Contact for More Information.

To read this article in its entirety click here.