R is considered the predominant language for data scientist and statisticians. Learn how to use R for your own data science projects.
Slow x64 application installation
I have recently reinstalled Windows7 x64 on a Lenovo T440p laptop.
Can install x32 applications without issue. However, installing x64 applications is painfully slow.
Have tried:
Running installer as administrator
Disabling Norton Antivirus (Auto protection and firewall)
Other possible related issues:
Novastor Backup gets stuck 'Creating Open File shadow copies'
Richard
Can install x32 applications without issue. However, installing x64 applications is painfully slow.
Have tried:
Running installer as administrator
Disabling Norton Antivirus (Auto protection and firewall)
Other possible related issues:
Novastor Backup gets stuck 'Creating Open File shadow copies'
Richard
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
For the most part, applications remain 32-bit. Microsoft continues to recommend Office 32-bit, so Adobe should also be 32-bit.
I have 64-bit drivers that install fine, 64-bit NCP (VPN) that installs fine, 64-bit WinZip that installs fine and few more 64-bit applications that install fine.
What are you have difficulty with?
I use Corporate Symantec Endpoint (not Norton Consumer) and I do not use Novastor backup. Since it appears to have a problem, can you uninstall this while you test?
I have 64-bit drivers that install fine, 64-bit NCP (VPN) that installs fine, 64-bit WinZip that installs fine and few more 64-bit applications that install fine.
What are you have difficulty with?
I use Corporate Symantec Endpoint (not Norton Consumer) and I do not use Novastor backup. Since it appears to have a problem, can you uninstall this while you test?
I have recently reinstalled Windows7 x64 on a Lenovo T440p laptop. <-- Also you may need driver updates. Find Lenovo Software Update (should be in Control Panel) and run that. If need be, go to Lenovo Support for your model and download Software Update.
You do not need all it offers (do not need reach, share, password and those things), but get BIOS for sure, Chipset, Video, Audio, Hotkey, Auto Scroll and key updates.
You do not need all it offers (do not need reach, share, password and those things), but get BIOS for sure, Chipset, Video, Audio, Hotkey, Auto Scroll and key updates.
John & Manieya,
Thanks for your replies.
With regard to Lenovo Software Update that is installed and up to date. As is windows update.
It is beginning to look like the issue is not actually x64 applications, more ones that attempt to create a restore point. This tends to be the larger applications and by chance these were x64.
I have tried to manually create a restore point and it fails with the following error:
"The creation of a shadow copy has timed out. Try this operation again. (0x81000101)"
This combined with my backup issue stalling while creating shadow copies points to the 'Volume Shadow Copy service'.
The service is started. I do see some entries in the event log:
"Applications: The VSS service is shutting down due to idle timeout."
Should I close this question and resubmit with VSS subject?
Thanks for your replies.
With regard to Lenovo Software Update that is installed and up to date. As is windows update.
It is beginning to look like the issue is not actually x64 applications, more ones that attempt to create a restore point. This tends to be the larger applications and by chance these were x64.
I have tried to manually create a restore point and it fails with the following error:
"The creation of a shadow copy has timed out. Try this operation again. (0x81000101)"
This combined with my backup issue stalling while creating shadow copies points to the 'Volume Shadow Copy service'.
The service is started. I do see some entries in the event log:
"Applications: The VSS service is shutting down due to idle timeout."
Should I close this question and resubmit with VSS subject?
You can keep this question here for a while. If there is another topic area you wish added, let us know.
Try running System File Checker. Open cmd.exe with Run as Administrator and run SFC /SCANNOW twice. Allow to complete,
Go to Computer, right click for Properties, then Advanced System Settings, System Protection, Click on Configure.
You have some choices here: You can turn OFF protection, restart and turn it back ON. You can delete Restore Points. The first choice will also delete restore points. Once you set (do not leave protection OFF), restart and test Restore Points again.
Try running System File Checker. Open cmd.exe with Run as Administrator and run SFC /SCANNOW twice. Allow to complete,
Go to Computer, right click for Properties, then Advanced System Settings, System Protection, Click on Configure.
You have some choices here: You can turn OFF protection, restart and turn it back ON. You can delete Restore Points. The first choice will also delete restore points. Once you set (do not leave protection OFF), restart and test Restore Points again.
I don't know of any way to back up a restore point. If you cannot get back to a restore point, they are not any good anyway.
John,
I have not tried to go back to last restore point. Several applications installed and configured. so I don't know if it will work. Does it use VSS for restore or just create?
Result of 1st scan
I have not tried to go back to last restore point. Several applications installed and configured. so I don't know if it will work. Does it use VSS for restore or just create?
Result of 1st scan
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\System32>SFC /SCANNOW
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of them.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log
C:\Windows\System32>
Try running SFC a second time. How restore points are used depend upon the application so I cannot say for sure.
SFC sometimes cannot correct all the errors.
So go back to my post and delete restore points, get rid of the page file, restart and make a new page file in the System Protection tab.
So go back to my post and delete restore points, get rid of the page file, restart and make a new page file in the System Protection tab.
You reinstalled Windows and it is screwed up.
You ran SFC and that did not fix things.
You deleted the page file and restore points, set them up as suggested and you still cannot use restore after that.
I can only see two options.
1. Run DISM (does not always work in Windows 7).
Open cmd.exe with Run as Administrator.
DISM.exe /Online /Cleanup-Image /Scanhealth (takes 15 - 20 minutes).
DISM.exe /Online /Cleanup-Image /Restorehealth (takes 15 - 20 minutes).
Restart the computer and test.
2. If that fails, back up and reinstall again.
You ran SFC and that did not fix things.
You deleted the page file and restore points, set them up as suggested and you still cannot use restore after that.
I can only see two options.
1. Run DISM (does not always work in Windows 7).
Open cmd.exe with Run as Administrator.
DISM.exe /Online /Cleanup-Image /Scanhealth (takes 15 - 20 minutes).
DISM.exe /Online /Cleanup-Image /Restorehealth (takes 15 - 20 minutes).
Restart the computer and test.
2. If that fails, back up and reinstall again.
John,
Issue seems to be with vss writers. When I try to check using vssadmin list writes I get the following message then nothing (have left running > 8hrs)
"Waiting for responses.
These may be delayed if a shadow copy is being prepared."
Do you think I need to close this now an reopen as a vss quetsion?
Issue seems to be with vss writers. When I try to check using vssadmin list writes I get the following message then nothing (have left running > 8hrs)
"Waiting for responses.
These may be delayed if a shadow copy is being prepared."
Do you think I need to close this now an reopen as a vss quetsion?
Do you think I need to close this now an reopen as a vss quetsion?
You can try that.
You might also consider checking the hard drive. Why? VSS writes are disk operations.
You might also consider reinstalling Windows. Why? None of the standard repair methods are working.
You can try that.
You might also consider checking the hard drive. Why? VSS writes are disk operations.
You might also consider reinstalling Windows. Why? None of the standard repair methods are working.
John,
Tried to 'repair' Windows using recovery discs, but only allows clean install. Tried (Almost successfully) to use a retail disc for Win7 Pro 64. This fixed the issue, but OEM key was not able to activate the repaired install.
Reluctantly ended up wiping and performing clean install from recovery discs.
Richard
Tried to 'repair' Windows using recovery discs, but only allows clean install. Tried (Almost successfully) to use a retail disc for Win7 Pro 64. This fixed the issue, but OEM key was not able to activate the repaired install.
Reluctantly ended up wiping and performing clean install from recovery discs.
Richard
Premium Content
You need an Expert Office subscription to comment.Start Free Trial