New
#51
Local Disk (C:)
Local Disk (C:)
Very odd - that should have come up on your listing above somewhere?
Please post a Disk Management screenshot - Disk Management - Post a Screen Capture Image
.PNG ponged
They didn't all appear in the first this includes F: and loses the WD Unlocker
Egads!
It looks as if the Windows partition/drive in the Recovery Environment should after all be the C: drive - in which case the proper command for the DISM should be
DISM /Image:C:\ /ScratchDir:C\ /Cleanup-Image /RevertPendingActions
PLease try that, and post back with the exact error message - if any. (note the space in there!)
Window heading: Administrator:X:\windows\system32\cmd.exe
DIR C:\$W*.* Volume in Drive C has no label.
Volume Serial No, is ........
Directory of C:\
File not found
DISM /Image:C:\ /ScratchDir:C\ /Cleanup-Image /RevertPendingActions
Deployment Image Servicing ??? Management tool (??? sorry can't read my own scribble
but thought not essential)
Version: 6.1.7601.17514
Error: 267
An error occurred while accessing the temporary directory.
Ensure that the patch to the directory exists and that you have Read/Write permissions on the folder.
For more information refer to the Help by running DISM.exe /ScratchDir /?_
BOTHER (and other euphemisms!) - I thought I'd checked for typos!
Try this command - hopefully it'll work...
DISM /Image:C:\ /ScratchDir:C:\ /Cleanup-Image /RevertPendingActions
Probably shouldn't mention (?) but I queried this :C:\ in #47
Deployment Image Servicing and Management tool
Version: 6.1.7601.17514
Image Version: 6.1.7601.18489
Reverting pending actions from the image ...
The operation completed. Any reverting of pending actions will be attempted after reboot.
The operation completed successfully.
Nope.
Kaspersky still won't open - they tell me it's dependent on .NET Framework.
My computer still opens without demanding a password.
I've still an important update that can't be made.
Microsoft should be phoning me 10 am tomorrow: I made the request last week, a four day wait was the best offered: but then they were due to phone me on the 23rd July between 10 and 11 am - but they didn't.
I tried for their chat line but last time there was a 5 hour wait.
I know it isn't solved yet but you've been far more help than they have- until they got involved I had a password and Kaspersky.