Yes, that is all I changed. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
But in the forum I found it in, someone suggested deleting/renaming all occurrences
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, July 08, 2015 2:41 PM
To: Midrange Systems Technical Discussion
Subject: RE: Attempt to load service pack for IBM i Access for Windows ends with "A system restart is pending, you must restart the computer before installing IBM i Access for Windows 7.1."
That is mentioned as circumvention 2.
Summary:
Do I just need to change
HKLM (aka HKEY_LOCAL_MACHINE)
SYSTEM, CurrentControlSet, Control, Session Manager
PendingFileRenameOperations REG_MULTI_SZ
\??\C:\Windows\system32\QIPCAP64.dll
Detail:
I searched the registry and found these entries:
HKLM (aka HKEY_LOCAL_MACHINE)
SYSTEM, ControlSet001, Control, BackupRestore, KeysNotToRestore
Pending Rename Operations REG_MULTI_SZ
CurrentControlSet\Control\Session Manager\PendingFileRenameOperations
Pending Rename Operations2 REG_MULTI_SZ
CurrentControlSet\Control\Session Manager\PendingFileRenameOperations2
SYSTEM, ControlSet001, Control, Session Manager ###PendingFileRenameOperations REG_MULTI_SZ \??\C:\Windows\system32\QIPCAP64.dll
PendingFileRenameOperations REG_MULTI_SZ
\??\C:\Windows\system32\QIPCAP64.dll
SYSTEM, ControlSet002, Control, BackupRestore, KeysNotToRestore
Pending Rename Operations REG_MULTI_SZ
CurrentControlSet\Control\Session Manager\PendingFileRenameOperations
Pending Rename Operations2 REG_MULTI_SZ
CurrentControlSet\Control\Session Manager\PendingFileRenameOperations2
SYSTEM, ControlSet002, Control, Session Manager ###PendingFileRenameOperations REG_MULTI_SZ \??\C:\Windows\system32\QIPCAP64.dll
PendingFileRenameOperations REG_MULTI_SZ
\??\C:\Windows\system32\QIPCAP64.dll
SYSTEM, CurrentControlSet, Control, BackupRestore, KeysNotToRestore
Pending Rename Operations REG_MULTI_SZ
CurrentControlSet\Control\Session Manager\PendingFileRenameOperations
Pending Rename Operations2 REG_MULTI_SZ
CurrentControlSet\Control\Session Manager\PendingFileRenameOperations2
SYSTEM, CurrentControlSet, Control, Session Manager ###PendingFileRenameOperations REG_MULTI_SZ \??\C:\Windows\system32\QIPCAP64.dll
PendingFileRenameOperations REG_MULTI_SZ
\??\C:\Windows\system32\QIPCAP64.dll
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Smith, Mike" <Mike_Smith@xxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 07/08/2015 01:48 PM
Subject: RE: Attempt to load service pack for IBM i Access for
Windows ends with "A system restart is pending, you must restart the
computer before installing IBM i Access for Windows 7.1."
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Rob,
I had this issue also, and resolved this by renaming the registry key
PendingFileRenameOperations, then install. As I recall the
PendingFileRenameOperations will be rebuilt.
Mike
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Wednesday, July 08, 2015 11:08 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Attempt to load service pack for IBM i Access for Windows ends
with "A system restart is pending, you must restart the computer before
installing IBM i Access for Windows 7.1."
Start, All Programs, IBM i Access for Windows, IBM i Access for Windows
Properties shows that I am currently at 7.1, SI50567.
I tried Check Service Level and it shows that I should be at SI56695. I
told it to proceed.
Several screens later I get a screen with the message:
"A system restart is pending, you must restart the computer before
installing IBM i Access for Windows 7.1."
I dutifully shutdown and try it again.
I get the same message.
Tried a google search for that message and the only hit I got was on a
Chinese wiki and google looks like they gave up on trying to translate
that.
I broke down the google search into
"system restart is pending" "IBM i Access for Windows"
and found APAR#: II14561
http://www-912.ibm.com/n_dir/nas4apar.NSF/c79815e083182fec862564c00079d117/6003b72afe84d2c9862576fd003c6d66?OpenDocument
I tried copying the stuff locally on the off chance that the note way at
the bottom about a different issue with a shared drive was the culprit.
That didn't help.
Going to try circumvention 1...
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
NOTICE: This message, including any attachment, is intended as a
confidential and privileged communication. If you have received this
message in error, or are not the named recipient(s), please immediately
notify the sender and delete this message.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
NOTICE: This message, including any attachment, is intended as a confidential and privileged communication. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this message.