Windows 10: Any changes happen in Sept 2018 that might break VSS?

Helping out a friend with a Lenovo Thinkpad T410. Came from the factory with Windows 7 Home and auto updated to Windows 10. He asked me to look at it this week after Windows Update installed KB4483234 and he could no longer logon, logonui.exe stopped working error messages found in event viewer after I corrected the problem.

One of the things I found was his Acronis 2017 full drive backups to an external USB connected drive were failing since September 2018 with "unknown errors". Looking at event viewer against his Crucial SSD showed I/O errors, Sector 41,306,704 unknown status (0x9) Failed to read snapshot (0x10c45a). I then ran an Acronis VSS diagnostic program that reported VSS ASR was failing. The only way to correct the problem was to remove the hidden factory restore partition for Windows 7 from the drive. Since the Acronis backups worked perfectly for at least one year until September 2018 I was wondering if something changed in Windows 10 that affected how Windows 10 VSS services handle hidden factory restore partitions? I'm a little out of my league here so please excuse me if I've enhanced the confusion factor in my description of this failure. - Steve, 73 de

:)

 

Windows 10 Lenovo laptop VSS backup issue

Using 3rd party backup solution to perform Volume Shadow Copy service ("VSS") failed.

Just happen of the Lenovo laptop contains OEM partitions. Is VSS support OEM partitions? Any official documentation mention?

Thanks.

-laptop Windows 10 Pro.

-VSS backup fails with error message

2018/08/22-10:16:05.69000 [uvss_assist] VssClient::ApplyDRRequirements: ASR Writer is selected for backup

2018/08/22-10:16:05.69000 [uvss_assist] - Checking volume \\?\globalroot\device\harddiskvolume2\ to see if mountpoint...

2018/08/22-10:16:05.69000 [uvss_assist] - Get volume path name for \\?\globalroot\device\ ...

2018/08/22-10:16:05.69099 [uvss_assist] Executing Win32 call 'L"GetVolumePathNameW"'

2018-08-22 03:16:05 avvss Error <8801>:

ERROR: Win32 call L"GetVolumePathNameW" failed.

2018/08/22-10:16:05.69099 [uvss_assist] - GetLastError() == 123

2018/08/22-10:16:05.69099 [uvss_assist] Loaded the VSS message DLL

2018/08/22-10:16:05.69099 [uvss_assist] - Error text: The filename, directory name, or volume label syntax is incorrect.

2018-08-22 03:16:05 avvss Error <12077>: VSS returned an error message exiting HR = 0x8007007b

2018-08-22 03:16:05 avvss Info <0000>: Finished with backup. Performing cleanup.

-No windows event ID error both applcation and system.

DISKPART> list disk

Disk ### Status Size Free Dyn Gpt

-------- ------------- ------- ------- --- ---

Disk 0 Online 238 GB 0 B *

DISKPART>

DISKPART>

DISKPART> exit

Leaving DiskPart...

C:\WINDOWS\system32>vssadmin list volumes

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool

(C) Copyright 2001-2013 Microsoft Corp.

Volume path: \\?\Volume{64cfe1e7-ca43-4207-8ef9-b8f1e4d3dfe5}\

Volume name: \\?\Volume{64cfe1e7-ca43-4207-8ef9-b8f1e4d3dfe5}\

Volume path: C:\

Volume name: \\?\Volume{f733ef78-05b5-4cdf-90d7-ff4f19d9156e}\

Volume path: \\?\Volume{a8d50436-c290-4e18-9371-287b0690c356}\

Volume name: \\?\Volume{a8d50436-c290-4e18-9371-287b0690c356}\

 

Jigsaw jam for Sept 7, 2018

On Sept 7, 2018, the daily game for jigsaw jam is not working correctly. When are you fixes this?????

Moved from: Windows / Windows 10 / Ease of access

 

How to factory reset Cisco 1700 Router

Hopefully I can help you here....its a very common thing to happen.


First, I take it you dont know the passwords for console access or telnet/ssh?

I will assume that these devices belong to you.

step 1. Plug a cisco console cable into a serial port on your pc
step 2. Plug other end into Cisco console port
step 3. Using hyperterm or putty or similar connect to the serial port
step 4. boot router, and make sure you clearly can see the output (this confirms you have good serial comms)
step 5. if this fails, adjust the comm port settings (9600, 8,1,n are the default)
step 6. now you have to do the only hard part...send the break command:

Break command list: Break Commands

Go down the list and match your OS and SW and try the sequence suggested.

If this fails several times do what I do: Install putty (free) and then to send a break so you can get into rommom just hit "ctrl-a b".