Page 7 of 15 FirstFirst ... 56789 ... LastLast

  1. Join Date : Oct 2013
    Posts : 16,448
    64-bit Windows 10 Pro build 14971
       2016-09-06 #60

    Will do. Hopefully, I can track down why it's not working for some soon.

    I just tested on a W10 Pro version 1607 build 14393.105 VM, and the script works on it as well.
      My System SpecsSystem Spec


  2. Join Date : Sep 2016
    Posts : 27
    Windows 10
       2016-09-06 #61

    The Event Viewer shows "Event 8193"

    Code:
    Volume Shadow Copy Service error: Unexpected error calling routine QueryFullProcessImageNameW.  hr = 0x80070006, The handle is invalid.
    
    Operation:
       Executing Asynchronous Operation
    
    Context:
       Current State: DoSnapshotSet
    
    *******************************************************************************************
    Here is the XML details.........
    
    
     - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    
       - <System>
    
         <Provider Name="VSS" />  
    
        <EventID  Qualifiers="0">8193</EventID> 
    
        <Level>2</Level> 
    
        <Task>0</Task> 
    
        <Keywords>0x80000000000000</Keywords> 
    
        <TimeCreated SystemTime="2016-09-06T12:18:02.441291700Z" /> 
    
        <EventRecordID>11519</EventRecordID> 
    
        <Channel>Application</Channel> 
    
        <Computer>Surface</Computer> 
    
        <Security />  
    
       </System>
    
    
      - <EventData>
         <Data>QueryFullProcessImageNameW</Data> 
    
        <Data>0x80070006, The handle is invalid.</Data>  
    
        <Data>Operation: Executing Asynchronous Operation Context: Current State:  DoSnapshotSet</Data> 
    
        <Binary>2D20436F64653A20534543534543524330303030303537392D2043616C6C3A20534543534543524330303030303536332D205049443A202030303030333830382D205449443A202030303030393131362D20434D443A2020433A5C57494E444F57535C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>  
    
       </EventData>
    
    
       </Event>
    Last edited by Brink; 2016-09-06 at 09:57. Reason: code box
      My System SpecsSystem Spec


  3. Join Date : Oct 2013
    Posts : 16,448
    64-bit Windows 10 Pro build 14971
       2016-09-06 #62

    @thekochs,

    Is you user profile folder still in the default "C:\Users" folder, and not moved to another location?


    If you would like to test, I think I may have found something else to see if the script may be failing when trying to resolve the SID of the writer.

    1) Open Registry Editor (regedit), and go to the key below.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

    2) Look for the SID key (ex: S-1-5-21-2423704721-1541669065-2985363390-1001) that has the ProfileImagePath string value for your account's profile folder.

    3) If you have another SID key with the same SID number with only .bak on the end (ex: S-1-5-21-2423704721-1541669065-2985363390-1001.bak), then this may be the issue.

    4) Delete only the SID key with .bak on the end, and restart the computer. It is safe to delete only this key since it's only a backup of the currently used SID without .bak for your account's profile.

    5) Test the script again to see if it works now.

    Click image for larger version. 

Name:	regedit.png 
Views:	22 
Size:	44.1 KB 
ID:	100158
      My System SpecsSystem Spec


  4. Join Date : Sep 2016
    Posts : 27
    Windows 10
       2016-09-06 #63

    Brink said: View Post
    Is you user profile folder still in the default "C:\Users" folder, and not moved to another location?
    YES, in Default

    Brink said: View Post
    If you would like to test, I think I may have found something else to see if the script may be failing when trying to resolve the SID of the writer.
    1) Open Registry Editor (regedit), and go to the key below.
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
    2) Look for the SID key (ex: S-1-5-21-2423704721-1541669065-2985363390-1001) that has the ProfileImagePath string value for your account's profile folder.
    3) If you have another SID key with the same SID number with only .bak on the end (ex: S-1-5-21-2423704721-1541669065-2985363390-1001.bak), then this may be the issue.
    4) Delete only the SID key with .bak on the end, and restart the computer. It is safe to delete only this key since it's only a backup of the currently used SID without .bak for your account's profile.
    5) Test the script again to see if it works now.
    I don't have the SID key: S-1-5-21-2423704721-1541669065-2985363390-1001
    ....take a look at snapshotClick image for larger version. 

Name:	2016-09-06_114359.jpg 
Views:	25 
Size:	428.2 KB 
ID:	100162

    The ProfileImagePath key is there under "my" -1001 SID key but no .BAK version of SID.
    Last edited by thekochs; 2016-09-06 at 11:42.
      My System SpecsSystem Spec


  5. Join Date : Oct 2013
    Posts : 16,448
    64-bit Windows 10 Pro build 14971
       2016-09-06 #64

    The SID would be unique per account per system, but that's ok. You didn't have one with .bak, so it rules that thought out.
      My System SpecsSystem Spec


  6. Join Date : Oct 2013
    Posts : 16,448
    64-bit Windows 10 Pro build 14971
       2016-09-06 #65

    @thekochs,

    Ok. One more thing to test if you like.

    Do you have system protection turned on for other drives than just the Windows C: drive?

    If so, turn off system protection for all drive but C: to see if you area able to successfully have a restore point created by the script.

    One of our other members Kari has reported this was the case for him, but they still work for me though.
      My System SpecsSystem Spec


  7. Join Date : Oct 2013
    A Finnish ex-pat in Germany
    Posts : 9,050
    Windows 10 Pro
       2016-09-06 #66

    Brink said: View Post
    One of our other members Kari has reported this was the case for him, but they still work for me though.
    I found it so incredible and illogical I had to capture it to video. It's unedited, just showing that if I have system protection enabled only for drive C: the scripts in this tutorial work perfectly creating a restore point, but as soon as I enable protection for another drive no restore points will be created.

    Again disabling protection from other drives, restore points will be created. A total mystery. I of course understand that this what happens on my machines may not apply to yours.

      My System SpecsSystem Spec


  8. Join Date : Sep 2016
    Posts : 27
    Windows 10
       2016-09-06 #67

    Brink said: View Post
    @thekochs,

    Ok. One more thing to test if you like.

    Do you have system protection turned on for other drives than just the Windows C: drive?

    If so, turn off system protection for all drive but C: to see if you area able to successfully have a restore point created by the script.

    One of our other members Kari has reported this was the case for him, but they still work for me though.
    I only have a C: HDD to choose from....no others in system.
    There IS a microSD card in my Surface micro SD slot that shows in File Explorer at "S:" (letter I assigned to it) but this does not show in System Restore as viable HDD for selection.....see snapshot below.
    However, not sure how script works but since my "C HDD" is only maybe my system thinks like Kari it is "all".
    Also, it would be good for Kari to show his "Event Viewer" for the times that the restore point was not created to see if he gets the same VSS error I got.

    Click image for larger version. 

Name:	CP.jpg 
Views:	23 
Size:	370.7 KB 
ID:	100243

    I hope you fix this and I see you in your script where you ID the O/S at W10 then do specific things.
    If GetOS = "Windows 10" Then
    Are you sure that 100% it will ID the O/S correctly and not some escape where the W10 "THEN" section is not run ?
    If it wasn't run then what would be the results for the "ELSE" if was really W10 but not IDed as such ?

    Also, something clearly changed in the W10 Version 1607 14393.82 to .105 build which is affecting your script calls.
    https://support.microsoft.com/en-us/...update-history
    I also had "Surface" updates to firmware/drivers but those were all power management items.
    ....since no other user has said they are on a Surface Pro 4 I assume it is MS update change.
    Here is detailed link of the August 30th cum KB: https://support.microsoft.com/en-us/kb/3176938
    Scroll down and you can download the Excel (csv) file of all the files that were updated in this KB.

    In mean time I have taken my RP Task Scheduler item I created for daily (5pm) creation and just entered this command line instead of pointing to your VBS script. With the /c included it terminates process when done.
    So, I get small window at 5pm a day when this runs and it closes when complete.
    cmd.exe /c "wmic.exe /Namespace:\\root\default Path SystemRestore Call CreateRestorePoint "My Shortcut Restore Point", 100, 7"

    Just so we are on same page this is the scrip of yours I'm running from my Desktop.
    I copied it out of your ZIP and run it from there.Click image for larger version. 

Name:	script.jpg 
Views:	19 
Size:	561.7 KB 
ID:	100247

    I went ahead and cleared my Event Viewer for you and ran this script from Desktop.
    It did not create Restore Point but there is Event info..........
    Click image for larger version. 

Name:	event.jpg 
Views:	32 
Size:	375.1 KB 
ID:	100248
    Last edited by thekochs; 2016-09-06 at 21:53.
      My System SpecsSystem Spec


  9. Join Date : Oct 2013
    Posts : 16,448
    64-bit Windows 10 Pro build 14971
       2016-09-06 #68

    @thekochs,

    If you're still up for testing, here's a stripped down to the bare basics .vbs file to run and see if it will now actually successfully create a restore point for you. This will help to see if some other part of the original script may be causing the error for you.

    Test_W10_CreateRP-Success_Message.vbs
      My System SpecsSystem Spec


  10. Join Date : Jan 2015
    UK, Midlands
    Posts : 6,192
    Win 10 Pro (1607)
       2016-09-07 #69

    Hi, I have this running fine on C: + D: - on a previous PC, both were partitions on the same HDD, now on the same SSD.
    Just wondering if there's a difference between two partitions and two physical disks- although I can't begin to imagine why..

    Here's the vbs I'm using for confirmation.
    Scheduled_Instant_Restore_Point.zip

    Click image for larger version. 

Name:	Snap 2016-09-07 at 08.21.56.jpg 
Views:	44 
Size:	110.3 KB 
ID:	100272
      My System SpecsSystem Spec


 
Page 7 of 15 FirstFirst ... 56789 ... LastLast


Similar Threads
Tutorial Category
Shortcut Arrow Icon - Change, Remove, or Restore in Windows 10
How to Change, Remove, or Restore Shortcut Arrow Overlay Icon in Windows 10 A shortcut is a link to an item (such as a file, folder, or app) on your PC. You can create shortcuts and then place them in a convenient location, such as on the...
Tutorials
System Restore Point - Create in Windows 10
How to Create a System Restore Point in Windows 10 If you're having problems with Windows 10 on your PC, you can try to refresh, reset, or restore it. System Restore uses a feature called system protection that regularly creates and saves...
Tutorials
This PC Shortcut - Create in Windows 10
How to Create a This PC Shortcut in Windows 10 My Computer was changed to This PC in Windows 8.1 and Windows RT 8.1. You would open File Explorer to view This PC. In Windows 10, File Explorer now opens to Quick access by default instead of...
Tutorials
Build 10130, No Restore Point
I updated my build this morning to build 10130 and everything on my system seems to be running so nice and smooth that I wanted to create a restore point. When I open the System Protection pane to create a restore point, everything is grayed out and...
Windows Insider
Restoring from Restore point - still no luck
After many, many attempts... installs, reinstalls, upgrades, ISO installs, the whole journey, I still cannot get a restore point to restore without messing up! No problem creating, no problem actually restoring, from control panel or boot. But...
General Support
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd

All times are GMT -5. The time now is 03:09.
Find Us
Twitter Facebook Google+



Windows 10 Forums