Downloaded, installed and rebooted ok on Portege M400.

I have Vista SP1 RC installed (v658) on my X60t...and when trying to install this patch (KB943899) I get a message saying "does not apply to your system".

This would strongly suggest that KB943899 is already included in SP1.

Hi!

This morning I installed Vista SP1 RC on my Motion LE1600. Just like Benjamin posted earlier in these comments, the 'Sleep of Death' update (kb943899) will not install after applying the SP1 RC; I'm told it doesn't apply to my system.

Looking thru the updates on my LE1600, there is no record of kb943899.

Over on the Windows Vista Team Blog (see link below), Nick White indicates in his 4th comment to his own blog post that: "I do know that this update [kb943899] will be included in SP1 at RTM, I'm not certain that it made the RC in time for its release.... It's more likely the case that SP1 RC simply will not allow you to install this update and that you'll have to wait until the RTM to take advantage of it."

So, I'm guessing that the Sleep of Death update (kb943899) is not part of SP1 RC. But just guessing!

It would be helpful if someone who has yet to install SP1 RC, could install the Sleep of Death update (kb943899) before installing SP1 RC, then check their applied updates list to see whether kb943899 is in the list or not.

I hope I don't have to revert to the backup I made of the LE1600 before installing SP1 RC, just to install the Sleep of Death patch, only to then have to install SP1 RC again. But it wouldn't be the end of the world if I did. But perhaps we can save other GBM readers some time by working out whether they should install the Sleep of Death patch BEFORE applying SP1 RC.

Does anyone think I could successfully uninstall SP1 RC using the Programs and Features/Installed Updates/ Control Panel so I can install the Sleep of Death patch and reinstall SP1 RC? SP1 RC is, in fact, listed there (kb936330)...

Nick Whites post to the Windows Vista Team Blog:
http://windowsvistablog.com/blogs/windowsvista/archive/2007/12/11/improving-reliability-and-performance-update-preview-release-available-today.aspx

Many thanks for the great coverage, Warner! You rock!
-Peter

I just applied the patch and did some preliminary tests and I haven't encounter any issue. Before the patch, if I leave Wifi on, 1 out 3 times transition to sleep mode hangs my X61T. After the patch I put the machine into sleep around 10 times, with or without turning off wifi and haven't seen any problem. I will keep monitoring it and update this thread if the old issue appear again.

@Peter: I installed SP1 RC on my X61T before and had to uninstall it since it caused the machine to crash randomly. I was able to install kb943899 after I installed and uninstalled SP1.

I installed this update and all current MS updates.
Running Vista Ultimate 32-bit on a X61T.
*** Still getting sleep of death as pressing power button to put system to sleep (not hibernate).
System still becomes unresponsive, but disk hits continue.
Event log shows time of sleep request:

Information 12/13/2007 10:41:38 AM Microsoft-Windows-ResourcePublication 102 None The service temporarily stopped publishing because of a power event.

Other background tasks continue according event log for approximate 10 minutes, then the system reboots.

Error 12/13/2007 10:54:18 AM EventLog 6008 None The previous system shutdown at 10:51:04 AM on 12/13/2007 was unexpected.

Of interest, there is not blue screen of death event in the log as there was in reported failures previous to installing the update. Is Symantec Corporate Antivirus common to other people's machines failing?

For your edification, below is my event log in text form. I hope this update helped others. It certainly did not help my machine.
-------------------------------------------------------------------
Level Date and Time Source Event ID Task Category
Information 12/13/2007 10:54:18 AM EventLog 6013 None The system uptime is 102 seconds.
Information 12/13/2007 10:54:18 AM EventLog 6005 None The Event log service was started.
Information 12/13/2007 10:54:18 AM EventLog 6009 None Microsoft (R) Windows (R) 6.00. 6000 Multiprocessor Free.
Error 12/13/2007 10:54:18 AM EventLog 6008 None The previous system shutdown at 10:51:04 AM on 12/13/2007 was unexpected.
Information 12/13/2007 10:54:17 AM Microsoft-Windows-Security-Auditing 5038 System Integrity "Code integrity determined that the image hash of a file is not valid. The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error.

File Name: \Device\HarddiskVolume2\Windows\System32\drivers\tvtfilter.sys "
Information 12/13/2007 10:54:17 AM Microsoft-Windows-Security-Auditing 4672 Special Logon "Special privileges assigned to new logon.

Subject:
Security ID: SYSTEM
Account Name: SYSTEM
Account Domain: NT AUTHORITY
Logon ID: 0x3e7

Privileges: SeAssignPrimaryTokenPrivilege
SeTcbPrivilege
SeSecurityPrivilege
SeTakeOwnershipPrivilege
SeLoadDriverPrivilege
SeBackupPrivilege
SeRestorePrivilege
SeDebugPrivilege
SeAuditPrivilege
SeSystemEnvironmentPrivilege
SeImpersonatePrivilege"
Information 12/13/2007 10:54:17 AM Microsoft-Windows-Security-Auditing 4624 Logon "An account was successfully logged on.

Subject:
Security ID: SYSTEM
Account Name: LVA0513-7764CTO$
Account Domain: IBMPEERS
Logon ID: 0x3e7

Logon Type: 5

New Logon:
Security ID: SYSTEM
Account Name: SYSTEM
Account Domain: NT AUTHORITY
Logon ID: 0x3e7
Logon GUID: {00000000-0000-0000-0000-000000000000}

Process Information:
Process ID: 0x2c8
Process Name: C:\Windows\System32\services.exe

Network Information:
Workstation Name:
Source Network Address: -
Source Port: -

Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0

This event is generated when a logon session is created. It is generated on the computer that was accessed.

The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).

The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
- Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested."
Information 12/13/2007 10:54:17 AM Microsoft-Windows-Security-Auditing 4648 Logon "A logon was attempted using explicit credentials.

Subject:
Security ID: SYSTEM
Account Name: LVA0513-7764CTO$
Account Domain: IBMPEERS
Logon ID: 0x3e7
Logon GUID: {00000000-0000-0000-0000-000000000000}

Account Whose Credentials Were Used:
Account Name: SYSTEM
Account Domain: NT AUTHORITY
Logon GUID: {00000000-0000-0000-0000-000000000000}

Target Server:
Target Server Name: localhost
Additional Information: localhost

Process Information:
Process ID: 0x2c8
Process Name: C:\Windows\System32\services.exe

Network Information:
Network Address: -
Port: -

This event is generated when a process attempts to log on an account by explicitly specifying that account’s credentials. This most commonly occurs in batch-type configurations such as scheduled tasks, or when using the RUNAS command."
Information 12/13/2007 10:54:17 AM Microsoft-Windows-Security-Auditing 4902 Audit Policy Change "The Per-user audit policy table was created.

Number of Elements: 0
Policy ID: 0x1498c"
Information 12/13/2007 10:54:16 AM Microsoft-Windows-Security-Auditing 4624 Logon "An account was successfully logged on.

Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0

Logon Type: 0

New Logon:
Security ID: SYSTEM
Account Name: SYSTEM
Account Domain: NT AUTHORITY
Logon ID: 0x3e7
Logon GUID: {00000000-0000-0000-0000-000000000000}

Process Information:
Process ID: 0x4
Process Name:

Network Information:
Workstation Name: -
Source Network Address: -
Source Port: -

Detailed Authentication Information:
Logon Process: -
Authentication Package: -
Transited Services: -
Package Name (NTLM only): -
Key Length: 0

This event is generated when a logon session is created. It is generated on the computer that was accessed.

The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).

The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
- Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested."
Information 12/13/2007 10:54:16 AM Microsoft-Windows-Security-Auditing 4608 Security State Change "Windows is starting up.

This event is logged when LSASS.EXE starts and the auditing subsystem is initialized."
Error 12/13/2007 10:54:21 AM Microsoft-Windows-Eventlog 1101 Event processing Audit events have been dropped by the transport. The real time backup file was corrupt due to improper shutdown.
Warning 12/13/2007 10:45:18 AM Symantec AntiVirus 6 None "

Could not scan 8 files inside C:\Users\Robert\AppData\Local\Microsoft\OneNote\Backup\Attachments\TraciWDLog_060707 (On 7-28-2007).zip due to extraction errors encountered by the Decomposer Engines."
Warning 12/13/2007 10:44:21 AM Symantec AntiVirus 6 None "

Could not scan 2 files inside C:\SWTOOLS\OSFIXES\VISTA\KB931573\KB931573-x86.msu due to extraction errors encountered by the Decomposer Engines."
Warning 12/13/2007 10:44:10 AM Symantec AntiVirus 6 None "

Could not scan 4 files inside C:\SWTOOLS\OSFIXES\VISTA\KB931573\KB931573-x64.msu due to extraction errors encountered by the Decomposer Engines."
Information 12/13/2007 10:43:28 AM Microsoft-Windows-WLAN-AutoConfig 8003 None "WLAN AutoConfig service has successfully disconnected from a wireless network.

Network Adapter: Intel(R) Wireless WiFi Link 4965AGN #2
Interface GUID: {3F5CA816-2FCE-4926-89F1-DA68DC3465FA}
Connection Mode: Automatic connection with a profile
Profile Name: Xtreme Calvin
SSID: Xtreme Calvin
BSS Type: Infrastructure
Reason: The network is disconnected by the driver.
"
Information 12/13/2007 10:43:17 AM Microsoft-Windows-WLAN-AutoConfig 11004 None "Wireless security stopped.

Network Adapter: Intel(R) Wireless WiFi Link 4965AGN #2
Interface GUID: {3F5CA816-2FCE-4926-89F1-DA68DC3465FA}
Local MAC Address: 00:13:E8:21:69:05
Network SSID: Xtreme Calvin
BSS Type: Infrastructure
Peer MAC Address: 00:15:E9:69:01:E3
Security Hint: The operation succeeds.
"
Warning 12/13/2007 10:42:28 AM Symantec AntiVirus 6 None "

Could not scan 7386 files inside C:\SWTOOLS\DRIVERS\TPBTooth\Win64\Data1.cab due to extraction errors encountered by the Decomposer Engines."
Information 12/13/2007 10:42:18 AM Microsoft-Windows-ResourcePublication 104 None The service is publishing to the network.
Warning 12/13/2007 10:42:16 AM Microsoft-Windows-WindowsUpdateClient 29 Windows Update Agent Windows Update lost connectivity.
Warning 12/13/2007 10:42:15 AM Symantec AntiVirus 6 None "

Could not scan 7386 files inside C:\SWTOOLS\DRIVERS\TPBTooth\Win32\Data1.cab due to extraction errors encountered by the Decomposer Engines."
Information 12/13/2007 10:41:42 AM Microsoft-Windows-TaskScheduler 124 Task triggered by locking the workstation "The description for Event ID 124 from source Microsoft-Windows-TaskScheduler cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:


The substitution string for insert index (%1) could not be found
"
Information 12/13/2007 10:41:41 AM Microsoft-Windows-Kernel-Power 42 None The system is entering sleep.
Information 12/13/2007 10:41:38 AM Microsoft-Windows-ResourcePublication 102 None The service temporarily stopped publishing because of a power event.
Information 12/13/2007 10:41:38 AM Service Control Manager 7036 None The Windows Image Acquisition (WIA) service entered the paused state.

Just want to give you guys a quick update: the sleep function have worked flawlessly in the past two days after the patch, with or w/o wifi on. This was the last gripe that I had with X61T/vista and hope the patch has completely cured this problem.

An update in case anyone is still paying attention (Ha!):

Previously, I asked:
"Does anyone think I could successfully uninstall SP1 RC using the Programs and Features/Installed Updates/ Control Panel so I can install the Sleep of Death patch and reinstall SP1 RC?"

The answer is YES! I've done it and now I have BOTH the Sleep of Death patch and Vista SP1 RC installed on my Motion LE1600.

I'm mentioning this only because my experience (along with Consolas & Matt - thanks guys!) may help save someone some time since the Sleep of Death patch cannot be installed on a system if SP1 RC is already installed.

Rock on!
peter