• [ Kill the Process, Use Killbox if your Access Denied ]

[In Windows Vista Run As Administrator, After Execution System Will Restart]

• %Windows\System32\ckvo.exe
• %Windows\System32\ckvo0.dll
• %Windows\System32\dllcache\cdaudio.sys
  
• %Documents and Settings\Default User\Local Settings\Temp\olhrwef.exe
• %Documents and Settings\Default User\Local Settings\Temp\nmdfgds0.dll
• %Root of Windows Installed Drive\86l2qw.bat
• %Root of Windows Installed Drive\yew.bat
  [ No Exact Information about Files, search above related files in Program files Folder ]
  If you have any of these files in running process from task manger, end the process before removal.
  Note: if task manager is disabled, Download the following file, Click to Download - Enable Registry.reg [ Right Click - Save Target As/Linked Content As ]
  Open it with Regedit.exe [%system32\regedit.exe], then it Confirms Add to registry Yes or No, Confirm Yes, then click Ok.

In addition to being Independence Day in Jamaica tomorrow :) , Microsoft will provide Windows 7 RTM to a select group of customers. Here is a quick reminder of the groups that can download it:

OEMs: ISV (Independent software vendor) and IHV (Independent hardware vendor) Partners will be able to download Windows 7 RTM from Microsoft Connect or MSDN on August 6th

ISVs and IHV partners: August 6 (downloadable via Microsoft Connect or MSDN)

Microsoft Gold certified resellers: August 16 (downloadable from the partner portal in English only); October 1 (other language)

TechNet/MSDN subscribers & Microsoft Connect: August 6 (English only); October 1 (other languages)

Windows 7 Technical Testers (invite only): August 6 (English only), if you selected retail box, you might not receive your copy until October 22nd or later because of the time it takes to manufacturer the product boxes.

Microsoft “Action Pack” subscribers: August 23 (English only); October 1 (remaining languages)

Volume licensees with existing Software Assurance license: August 7 (downloadable from the Volume License Service Center in English);

Volume licensees without a Software Assurance license: September 1 (downloadable from the Volume License Service Center)

Consumers: General availability begins October 22. Retailers and OEMs will be offering new systems preloaded with Windows 7 and copies of Windows 7 at retail on that day.

Resources:

Windows Anytime Upgrade and Family Pack Pricing details revealed
Dell Windows 7 Option Upgrade Program
More information on Windows 7: Pricing and Availability
Windows 7 Editions – More detailed information
Official: Microsoft Confirms Windows 7 Editions

Hi everyone!

My name is Gary Schare and I run our hardware ecosystem marketing team. Building on Mark’s recent post on software readiness, I wanted to provide a deeper look at hardware readiness.

Hardware compatibility is a critical feature of Windows 7. We must have strong support from the hardware ecosystem to ensure that all of you have a great experience using Windows 7 with the devices and peripherals you rely on every day. This experience can range from “it just works when I plug it in” to “it lights up a new feature of Windows 7” (like Device Stage, Play To, etc.). The ultimate endorsement of this experience is the “Compatible with Windows 7” logo which is earned by products that pass rigorous compatibility and reliability tests.

We have been working closely with hardware partners on readiness since very early on in Windows 7 development. These activities range from 1:1 technical engagement with top-tier OEMs and device makers, the Windows Ecosystem Readiness Program which scales out to tens of thousands of vendors, webinars and readiness events in the US, Asia, and Europe to assist our hardware partners as they prepare their products for the Windows 7 Logo.

All these efforts have paid off, and Windows 7 Logo momentum is very strong. We now have printers, scanners, networking cards, storage devices, video capture cards, and ultra mobile systems that have already earned the “Compatible with Windows 7” Logo, and many more on the way. Represented in this group of devices are some of the biggest names in the industry. Here are a few examples, organized by topic:

Home Networking

Home networking was once very intimidating for the average customer. That is why we have improved Windows Connect Now (known to the Windows hardware industry as Windows Rally) to help consumers easily set up a wireless network or add a device to the network in seconds. Top companies such as Linksys by Cisco and D-Link are taking advantage of this technology to help their customers.

The Linksys group at Cisco is integrating Windows Connect Now into new and currently shipping routers and network media devices. These devices will earn the “Compatible with Windows 7” logo.

Robert Berlin, Director, Home Networking and Peripheral Product Management, Cisco Consumer Business Group:

The Windows 7 platform approach to open standards, such as Wi-Fi Protected Setup (WPS), Universal Plug and Play (UPnP) and Digital Living Network Alliance (DLNA) help to enable easier connectivity of computers with home networking products such as our Linksys by Cisco routers and media entertainment products. We look forward to providing the added benefits of Windows 7 to our products for our customers to experience on their home networks. 

Other great companies like D-Link are also taking advantage of Windows Connect Now to help lower support calls for their products and create a streamlined set up experience for their customers.

Dan Kelley, D-Link:

The key to a great user experience is connectivity and Windows 7 provides D-Link with a platform and the proper resources to insure our devices provide a seamless connectivity experience out of the box.

Device Experiences

One of the great innovations in Windows 7 is Device Stage. Device Stage lets you see your device status and run common tasks from a single, branded window that’s customized for each device. Device manufacturers around the world are building customized experiences for Device Stage so their customers can easily discover new features in their devices (and even some old ones too!).

One of the many partners taking advantage of Device Stage is Sandisk.Their full line of Sansa portable media players support Device Stage allowing their customers to easily sync audio and video, access the user manual and forums, update firmware, purchase accessories, and more.

Greg Stevens, Director, Integration & QA, Sandisk:

We’re very excited for the upcoming launch. All our current and legacy Sansa portable media players support Windows 7. We also were the first company to earn the “Compatible with Windows 7” logo for any portable media players. The Sansa Clip, View, and Fuze have passed Microsoft testing for compatibility and reliability with Windows 7 under the Windows Logo Kit program.

Graphics Performance

Our partners have also been making lots of headway with Direct X. DirectX 11, introduced in Windows 7, provides an unprecedented visual experience for next-generation games on new hardware. It’s an experience that accelerates elegantly across multiple processor cores, display resolutions, memory con?gurations, and graphic adapters.

I’m especially excited by Advanced Micro Devices (AMD), which delivered the first DirectX 11 graphics processor! This is fantastic for the adoption of the DirectX 11 platform, and great news for all the gamers out there.

Ben Bar-Haim, Corporate Vice President, Software Engineering, AMD:

The development of Windows 7 has been a tremendously collaborative effort, with the Microsoft and AMD teams working together to help ensure that today's customer-centric platforms can take full advantage of Windows 7, as well as preparing Windows 7 for the rapidly evolving future of computer hardware. Everything from the development of DirectX 11, improved memory efficiency, superior display management, driver model robustness, and the new GPU acceleration infrastructure for desktop and scientific applications points to an advanced operating system designed to the needs of the computer industry for years to come.

And More …

There are many other partners getting ready for Windows 7 across a variety of device categories. To learn more about what they’re doing, you can visit ReadySet7.com where we’ve brought together stories and videos from our hardware and software partners. Here are a few examples.

Dwight Diercks, Vice President of Software Engineering at NVIDIA:

All of our hard work teaming with Microsoft over the past two years will pay off for NVIDIA GPU owners when Windows 7 launches. Our customers are demanding an experience that is faster and more visual, and the new GPU-accelerated features like DirectX Compute are sure to blow people away.

Hanoz Gandhi, Vice President of Products, Belkin:

Belkin is committed to giving our customers the ability to create a reliable network that seamlessly integrates with the upcoming release of Windows 7. We are working closely with Microsoft to test Windows 7 with our products and plan to provide support for Windows 7 after it’s publically available.

Ikuaki Kitabayashi, General Manager of Planning and Design, Epson:

One of the key innovations in Windows 7 is Device Stage, which brings together the formerly independent features of Epson’s multifunction printers into one location, allowing users to see device status and run common tasks from a single window, thereby providing seamless device usability. Also, a photo-realistic icon that represents their physical device further improves the ability to interact with Epson’s multifunction printers. With HomeGroup, Epson printers are easily shared with other PCs in the home, while being protected by dependable security measures. In addition, Epson’s network projectors support the Windows Network Projection feature in Windows 7. Finally, the Windows Rally program has really allowed Epson to focus on making the most of Windows 7’s advanced device management and networking features, and optimizing the user experience.

Tzumu Lin, CEO of WonderMedia Technologies, Inc:

We are pleased to offer support for Microsoft’s much-anticipated Windows 7 throughout our portfolio of feature-rich Networked Media Devices. Our WonderMedia PRIZM platform offers proven and certified building blocks for Windows 7-based devices, allowing end-users to enjoy the full Windows 7 experience and optimal system performance.

Scott Rader, Director of Product Management, WD Branded Products:

Our close working relationship with MSFT allowed us to take advantage of the features of Windows 7 to provide our customers a seamless, user-friendly experience while keeping their content secure and readily accessible.

Frank Martin, Sr. Director of Product Planning, Brother International Corp:

Windows 7 will take the user experience to the next level of features and usability. Brother is ready to utilize these new resources which can offer a truly rich user experience. We can’' wait for our customers to have such a great experience with Windows 7 and Brother Products.

James Brailean, PhD., CEO, Packetvideo:

PacketVideo is working with Windows 7 to leverage the innovations for Device Stage to enable consumers to enjoy their photo, video and music files on connected devices throughout the home without limitation or hassle. This is through PV’s TwonkyMedia server, a best-in-class solution that has been adopted by leading consumer electronics manufacturers in the industry, and mobile handset connectivity solutions to the PC.

RK Parthasarathy, Vice President of Marketing, Ubicom:

Ubicom is expanding the definitions of the connected home and digital lifestyle through our flexible, highly integrated technology for networking, media and peripheral functionality. The ability to interoperate with Windows 7 ahead of public release ensures compelling user experiences for our customers’ products when they hit the market.

Todd Antes, Vice President of Computing and Consumer Networking, Atheros:

Robust support for Windows 7 is another important way that Atheros is demonstrating our commitment to delivering the best possible wireless experience in devices throughout the digital home and in the growing array of computing products, including notebooks and netbooks. We are pleased to have obtained the Compatible with Windows 7 logo for both our networking and computing solutions.

RELATED BLOG POSTS:

• Partner Software Ecosystem Continues to Line Up to Support Windows 7
• An Ecosystem Update for Windows 7
  

Version checking is probably one of the most common Application Compatibility issues that both developers and users are facing. This is another post in a series of posts about Getting Ready for Windows 7.

As said, this is probably the most common application compatibility issue that users as well as developers face is when an application fails upon checking the operating system version. A lot can go wrong when version checking is misused. A user might experience a “silent fail” where the application simply fails to load and nothing happens. Or, a user might see a dialog box indicating something to the effect of “you must be running Microsoft Windows XP or later” when in fact, the computer is running Windows 7. Many other consequences to poor version checking can inconvenience users as well.

Applications fail due to version checking for two main reasons:

• A flaw (bug) in the version checking code, which fails if the minor version is decreased, even if the major version is increased, for example, changing versions from 5.1(Windows XP) to 6.0 (Windows Vista), or if the expected service pack (SP) is not installed, even if you're running a newer operating system (for example, changing versions from Windows XP SP 2 to Windows Vista SP 1). We recommend that you check functionality rather then checking version, as you can read in this post.
• An intentional blocking that prevents the application from running on operating system versions not tested by its developers. We recommend that you do not block applications from running on future operating systems.

When an application runs on an "incompatible" (due to poor version checking) version of Windows, it will generally display an error message, but it may also exit silently or behave erratically. Often, if we work around the version checking, the application will run well. End-users and IT professionals may apply a fix to let the application think it is running on an older version of Windows.

Working Around The Problem (not really solving the bug)

Compatibility mode: Designed for end users (not for developers to not fix their bugs), compatibility mode is an easy way to work around compatibility issues. When enabled, it applies a set of compatibility fixes that provide a runtime environment more compatible with applications written for older versions of Windows. One of those fixes is the "version lie," which makes the version query functions return the operating system version the user chose in the Compatibility tab of the Properties dialog box instead of the actual Windows version.

To enable compatibility mode:

• Right-click the executable or shortcut to the executable.
• Click Properties.
• Click the Compatibility tab.
• Enable Run this program in compatibility mode for: and select the operating system version you think the application should be able to run on.
  Some applications consist of several executables. You may need to apply this fix to each one.

• Click OK to close the dialog box.
• Run the application.

Checking for Features Rather Than Version

As mentioned previously, checking the operating system version is not the best way to confirm that a specific operating system feature is available. This is because the operating system may have had new features added in a redistributable DLL. Rather than using GetVersionEx to determine the operating system platform or version number, it is more effective to test for the presence of the feature itself. For example, we plan to make the Direct2D and DirectWrite APIs and the Ribbon API available in Windows Vista, so there is no need to block your application from using these APIs when running on Windows Vista. You just need to check if these features are available on the Operation System that you are running. If possible, your application should still run if the feature is unavailable, though with reduced functionality or performance.

You can use one of the following techniques to find out if a specific features is available on the given OS.

For Win32 developers:

• Use LoadLibrary() to load a library which is not yet loaded into your application. If you are interested in a new function of a DLL which is already loaded (for example, kernel32.dll), then call GetModuleHandle() to obtain the module handle. If either of these functions return NULL, then this indicates an error.
• Use GetProcAddress() to obtain a function pointer. If GetProcAddress() returns NULL, then the function may not exist. Cast the pointer to a function pointer of an appropriate prototype. Some functions, although they exist may actually be stubs that return a "not implemented" error. Be such to check for such errors.

Windows 7 introduces a new timer API - SetWaitableTimerEXProc, which adds one more input variable to the regular SetWaitableTimerProc. The TolerableDelay lets you specific a time tolerance window in which the timer can expire. This is a new in Windows 7, that we will use to demonstrate how to check for feature.

      // define function pointer type
    typedef BOOL (WINAPI *SetWaitableTimerExProc)(
      __in  HANDLE hTimer,
      __in  const LARGE_INTEGER *lpDueTime,
      __in  LONG lPeriod,
      __in  PTIMERAPCROUTINE pfnCompletionRoutine,
      __in  LPVOID lpArgToCompletionRoutine,
      __in  PREASON_CONTEXT WakeContext,
      __in  ULONG TolerableDelay
    );

    LARGE_INTEGER liDueTime;
    liDueTime.QuadPart = 0;
    nt period = 1000;
    unsigned int tolerance = 1000;
    HANDLE hTimer = // Get timer handle

    REASON_CONTEXT reasonContext = {0};
    reasonContext.Version = 0;
    reasonContext.Flags = POWER_REQUEST_CONTEXT_SIMPLE_STRING;
    reasonContext.Reason.SimpleReasonString = L"MyTimer";

    // Get module handle to a module which is already loaded
    HMODULE hKernel32Module = GetModuleHandle(_T("kernel32.dll"));
    if (hKernel32Module == NULL)
        return FALSE;

    // Get Address of function
    SetWaitableTimerExProc pFnSetWaitableTimerEx =
    (SetWaitableTimerExProc) ::GetProcAddress(hKernel32Module,     
        "SetWaitableTimerEx");

    // Check if the function exists    
    if (pFnSetWaitableTimerEx == NULL)
        return FALSE;

    // Call function
    if (!pFnSetWaitableTimerEx(hTimer, &liDueTime, period, NULL, NULL,
            &reasonContext, tolerance)
    { // handle error }

Alternatively, you may use DLL delayed loading and call functions in a __try...__except block. (For more information, see Linker Support for Delay-Loaded DLLs.)

For COM APIs, handle errors returned by CoCreateInstance and QueryInterface.NET framework applications that call Win32 APIs via P/Invoke should handle EntryPointNotFoundException and DllNotFoundException exceptions.

If You Must Check OS Version Number

Identifying the current operating system is not the best way to determine whether a particular operating system feature is present. However, if you can’t design your application to check for specific feature availability and the only way to ensure compatibility is through version checking, then please consider the following.

For native applications, you will need to ensure your application's logic will work with newer versions of Windows. Please DO NOT BLOCK on version change! The following is a Win32 code example that uses GetVersionEx. If the major version is greater than 5 (Windows Vista, Windows® Server 2008 R2 and Windows 7), the check passes. If it equals 5, then the minor version should be 1 or greater (Windows XP or Windows Server 2003).

#include <windows.h>
#include <stdio.h>

void main()
{
    OSVERSIONINFO osvi;
    BOOL bIsWindowsXPorLater;

    ZeroMemory(&osvi, sizeof(OSVERSIONINFO));
    osvi.dwOSVersionInfoSize = sizeof(OSVERSIONINFO);

    GetVersionEx(&osvi);

    bIsWindowsXPorLater = 
 ( (osvi.dwMajorVersion > 5) ||
       ( (osvi.dwMajorVersion == 5) && (osvi.dwMinorVersion >= 1) ));

    if(bIsWindowsXPorLater)
  printf("The system meets the requirements.\n");
    else printf("The system does not meet the requirements.\n");
}

However there is a better way to verify the minimum OS version required using VerifiyVersionInfo(). This function compares a set of operating system version requirements to the corresponding values for the currently running version of the system. The following code example uses VerifyVersionInfo to check the operating system version against minimal requirements (Windows XP SP2):

#include <windows.h>
BOOL Is_WinXP_SP2_or_Later () 
{
   OSVERSIONINFOEX osvi;
   DWORDLONG dwlConditionMask = 0;
   int op=VER_GREATER_EQUAL;

   // Initialize the OSVERSIONINFOEX structure.

   ZeroMemory(&osvi, sizeof(OSVERSIONINFOEX));
   osvi.dwOSVersionInfoSize = sizeof(OSVERSIONINFOEX);
   osvi.dwMajorVersion = 5;
   osvi.dwMinorVersion = 1;
   osvi.wServicePackMajor = 2;
   osvi.wServicePackMinor = 0;

   // Initialize the condition mask.

   VER_SET_CONDITION( dwlConditionMask, VER_MAJORVERSION, op );
   VER_SET_CONDITION( dwlConditionMask, VER_MINORVERSION, op );
   VER_SET_CONDITION( dwlConditionMask, VER_SERVICEPACKMAJOR, op );
   VER_SET_CONDITION( dwlConditionMask, VER_SERVICEPACKMINOR, op );

   // Perform the test.

   return VerifyVersionInfo(
      &osvi, 
      VER_MAJORVERSION | VER_MINORVERSION | 
      VER_SERVICEPACKMAJOR | VER_SERVICEPACKMINOR,
      dwlConditionMask);
}

In this code you can see how we use the VerifyVersion with a set of conditions to return TRUE incase we run on any OS grater than Windows XP Service Pack 2.

For .NET Framework developers, use the ==, !=, <=, <, >, >= operators of the Version object returned by Environment.OSVersion.Version:

// This code checks if the OS is at least Windows XP
  if (Environment.OSVersion.Version < new Version(5, 1))
  {
        MessageBox.Show("Windows XP or later required.",
         "Incompatible Operating System", MessageBoxButtons.OK,
                MessageBoxIcon.Error);
        return;
  }

It is highly recommended that you don’t check for version at all and try looking to work with features. It will prove valuable for the future…

Just incase you want to read more, here are some useful links

• Application Compatibility Cookbook: http://msdn.microsoft.com/en-us/library/bb963893.aspx
• Version Lie and Managed Applications: http://blogs.msdn.com/cjacks/archive/2007/09/10/version-lie-shims-and-managed-code-on-windows-vista.aspx

You can also download a HOL and code sample for this topic.

To keep myself from breaking things, or minimize the damage done when I open one of those “Flying Hamster” videos that has a virus hidden in it, I don’t login to Windows as an administrator

When I need to do something that requires admin access, I elevate that process by right clicking the program icon and selecting “Run as Administrator”

If you use a program many times through the day, it is nice to change the properties of that app and force it to run as administrator. That way you are automatically prompted when you launch it – no right clicking needed

This is where I got really frustrated with Vista. Do the same for the command prompt shortcut and everything is disabled on that page

For the longest time I could not figure out how to get the command prompt to auto-elevate. I even resorted to using this tool (Great tool BTW) to change the resources within the cmd.exe file to force it to run as administrator.

Today I re-installed my Vista machine for the 20th time, and I finally found out how you can do this – It was much simpler than I thought.

You right click on the command prompt icon, and go to properties.

Click on advanced

Then. SURPRISE! There is the option:

Woo Hoo! Now I don’t have to keep right clicking on the command prompt to elevate it.

It would appear that a conference sells out pretty fast when a free netbook with Windows 7 is up for grabs, as Microsoft TechEd Australia helped demonstrate over the past couple of weeks. If you’ve missed out however, there is another way to get in. Free as a matter of fact, and the odds are pretty good!

The Codemasons’ Guild, a fancy (but admittedly shorter) name for the Microsoft Australia Windows Mobile developers club, is hosting two separate competitions that gives three (3) Australian developers and two (2) Australian higher-education students an all-expense paid trip to TechEd plus extras.

The competitions wittingly named “Master Codemason” and “Student APPrentice” asks developers and students respectively to come up with an interesting Windows Mobile application idea that fits one of twelve broad categories. Although one could argue fart-noise applications falls into either “entertainment” or “health”, I’d personally advise against them.

Whilst the site is a little contradictory in its terminology, it’s my understanding that besides a brief text description of the application, you will also need to submit some functional code and screenshots/videos of the application running on device or emulator. It doesn’t have to be perfect however as part of the prize is some technical mentoring to ready the application to market, but don’t leave it at “Hello World” either.

The competition closes August 17 for students and August 21 for developers so you better get your thinking caps on. You can find more details including but not limited to the enthralling terms and conditions of the competition at the official website.