Defrag: TPM & Bitlocker, Search Service, How to Pick Wifi Hardware

Sign in to queue

The Discussion

  • User profile image
    Bryan

    Downgrading Windows edition. If he's REALLY concerned about being able to downgrade, he can use one of the many imaging tools such as Acronis True Image, Ghost, or even Windows Home Server to create an image before upgrading. Then he'll be able to just do a restore to effectively downgrade.

  • User profile image
    Magic​Andre1981

    I would run ProcMon to see why there is such delay after connecting the device. In ProcMon you can look at the Duration column to see what takes so long.


    To downgrade from a higher SKU to a lower SKU use this tool:

    http://mp7000.deviantart.com/art/Windows-7-Enterprise-Downgrade-159805048

    It changes some settings so that Windows thinks it is the lower SKU. Next run Setup.exe and choose Upgrade to start the InPlace Upgrade and now your higher SKu is downgraded to the lower SKU because windows thinks it does an Inplace upgrade to repair the lower SKU Big Smile


    If no WLANs can be found make sure the Wireless service is running. I also have a strange issue when I return from hibernation in Windows 7. Here my WLAN is also not shown, so I have to go to device manager, disable the WiFi card and enable the WiFi card again. Now I can connect to the WLAN without any issues. Looks like a Windows 7 bug but there is no fix for it. The user show try this too.


    And please change the link of the WAIK in the last show Wink

  • User profile image
    dtower

    iirc the pro sku doesn't have media center.  Maybe that's why?

  • User profile image
    Magic​Andre1981

    iirc the pro sku doesn't have media center.  Maybe that's why?

    no, this was in Vista. There the business didn't have the Media center. In Windows 7 all higher SKUs include the functions from the lower SKU.

  • User profile image
    davewill

    ,Magic​Andre1981 wrote

    I would run ProcMon to see why there is such delay after connecting the device. In ProcMon you can look at the Duration column to see what takes so long.

    Thanks MagicAndre1981, Gov, and Larry.  I watched the events in ProcMon and narrowed down the time frames.  It appears that the networking stack to the device takes 3 to 7 seconds (varies with each device connect) to become usable.  I setup a CMD window with "ping 169.254.2.1 -t" and could see where the device was unreachable (disconnected) then general failure (device was just connected) then ping results (device networking established) then after 3 or 4 successful pings the device's networking was generally available to other applications.

  • User profile image
    Magic​Andre1981

    1 thing where you want to do an downgrade is if users tried the Enterprise 90day trial, installed all their software and later bought a Home Premium license. But now they had to reinstall everything. Here makes the downgrade sense.

  • User profile image
    Ytterbium

    You can save your searches as well, which I found useful.

Add Your 2 Cents