VMMap v2.61: This fixes a minor bug in the calculation of the Unknown category total.

AdExplorer v1.3: This update to AdExplorer, an Active Directory editor, has major node expansion performance improvements and a number of minor bug fixes.

VMMap v2.6: VMMap, a powerful process virtual and physical memory analysis tool, now shows both graphical and numeric breakdowns of private virtual memory, as well as heap configuration flags.

... read more

Paul Thurrott Interviews Mark on Windows 7 Development: Check out Mark’s interview with Windows IT Pro Magazine columnist Paul Thurrott, where he discusses some of the thinking behind Windows 7.

Mark’s Blog: Case of the Slow Logon: Mark’s latest blog post documents a troubleshooting case that highlights the use of PsExec to monitor the

... read more

ProcDump v1.72: This update changes the dump file date and time format to be ISO compliant and fixes a bug that prevented ProcDump from exiting when the process termination condition was active.

Desktops v1.02: v1.02 works around another issue that could prevent Alt+Tab from working on alternate desktops on 64-bit Windows 7 systems.

... read more

Although we continue to innovate around all natural user interface input methods–including ink, multitouch, and handwriting recognition–the Tablet PC Team blog is no longer active. Instead, blog posts from our team members can be found on the Windows Team Blog (http://windowsteamblog.com/).

Thank you so very, very much.

We’ve been looking at various registry cleaner reviews lately and have found that there’s a tool called “RegCure” which seems to work very well to fix your Pc and stop a number of different errors. Being the inquisitve people we are, we decided to investigate this registry cleaner tool and found review of RegCure to be very helpful. This

... read more

One question we sometimes get asked is why Exchange changes PowerShell’s execution policy from “Restricted” to “RemoteSigned.” Doesn’t that lower PowerShell’s security?

The “Restricted” execution policy isn’t intended to be something that PowerShell users live with forever. It’s a safe default that protects non PowerShell users from being impacted by PowerShell-based malware.

For example, many home users had never used VBScript, but

... read more

One question we sometimes get asked is why Exchange changes PowerShell’s execution policy from “Restricted” to “RemoteSigned.” Doesn’t that lower PowerShell’s security?

The “Restricted” execution policy isn’t intended to be something that PowerShell users live with forever. It’s a safe default that protects non PowerShell users from being impacted by PowerShell-based malware.

For example, many home users had never used VBScript, but

... read more

One question we sometimes get asked is why Exchange changes PowerShell’s execution policy from “Restricted” to “RemoteSigned.” Doesn’t that lower PowerShell’s security?

The “Restricted” execution policy isn’t intended to be something that PowerShell users live with forever. It’s a safe default that protects non PowerShell users from being impacted by PowerShell-based malware.

For example, many home users had never used VBScript, but

... read more

One question we sometimes get asked is why Exchange changes PowerShell’s execution policy from “Restricted” to “RemoteSigned.” Doesn’t that lower PowerShell’s security?

The “Restricted” execution policy isn’t intended to be something that PowerShell users live with forever. It’s a safe default that protects non PowerShell users from being impacted by PowerShell-based malware.

For example, many home users had never used VBScript, but

... read more