Leaderboard

The internet of the future will just be like the internet of the past. When people first got AOL and didn't know there was something beyond AOL's walled garden.

I think we can make an exception for "stupid peoples", as it better conveys the incredible amount of them being around (and growing). In Italy we have a saying that would roughly translate to "the mother of imbeciles is always pregnant". jaclaz

Left-click on Add Drivers

Sorry, that sentence was about Vista and therefore OT here. I don’t think there is any way to install similar SHA-256 support on XP, so Idrassi as quoted above by Proteus probably does make a valid point with respect to XP support.

Finally I found the culprit. Since stop services and kill processes do not solve the problem, and the problem occurs after logging in, then it must be some device driver, as @RainyShadow said, but not the normal driver that loaded before logging in. I then used Autoruns, found in the device list ADS812S and ADSIO, which is used for Advantech's data card before, deleted them, and all standby and hibernation functions returned! The record in the previous powercfg /devicequery all_devices_verbose is attached, in which it seems nothing unusual. Enumerating Device: 175 =================== Device Information: DeviceName: ADS812S HardwareID(s): UNKNOWN Device Present. Device is not capable of waking the system. Device Power Capabilities: D0 supported D3 supported Device State Mappings: S0 -> D0 S1 -> D3 S2 -> D3 S3 -> D3 S4 -> D3 S5 -> D3 Derived System State Mappings: S0 supported S1 supported S2 supported S3 supported S4 supported S5 supported Address: Unavailable Bus Number: Unavailable Class GUID: {8ECC055D-047F-11D1-A537-0000F8753ED1} Compatible device ID(s): Unavailable Device Description: ADS812S Driver Name: {8ECC055D-047F-11D1-A537-0000F8753ED1}\0051 Device Enumerator: ROOT Device Location: Unavailable Lower Filter(s): Unavailable Upper Filter(s): Unavailable Service Name: ADS812S Security Description: Unavailable SPDRP_REMOVAL_POLICY: CM_REMOVAL_POLICY_EXPECT_NO_REMOVAL Hardware Removal Policy: CM_REMOVAL_POLICY_EXPECT_NO_REMOVAL Override Removal Policy: Unavailable Physical Device Object name: \Device\00000007 Manufacturer: Unavailable Enumerating Device: 176 =================== Device Information: DeviceName: ADSIO HardwareID(s): UNKNOWN Device Present. Device is not capable of waking the system. Device Power Capabilities: D0 supported D3 supported Device State Mappings: S0 -> D0 S1 -> D3 S2 -> D3 S3 -> D3 S4 -> D3 S5 -> D3 Derived System State Mappings: S0 supported S1 supported S2 supported S3 supported S4 supported S5 supported Address: Unavailable Bus Number: Unavailable Class GUID: {8ECC055D-047F-11D1-A537-0000F8753ED1} Compatible device ID(s): Unavailable Device Description: ADSIO Driver Name: {8ECC055D-047F-11D1-A537-0000F8753ED1}\0050 Device Enumerator: ROOT Device Location: Unavailable Lower Filter(s): Unavailable Upper Filter(s): Unavailable Service Name: ADSIO Security Description: Unavailable SPDRP_REMOVAL_POLICY: CM_REMOVAL_POLICY_EXPECT_NO_REMOVAL Hardware Removal Policy: CM_REMOVAL_POLICY_EXPECT_NO_REMOVAL Override Removal Policy: Unavailable Physical Device Object name: \Device\00000008 Manufacturer: Unavailable

WinNTSetup 5.0 Beta 4 - fixed various bug on Windows 7 Host - fixed WinRE could not display PNG compressed icons - fixed MessageBox font on Windows 11 - fixed tweaks incorrectly loaded from ini - lighter disk access during disk scanning