Windows 10 Hyper-V VSS Writer

Discussion in 'Windows 10' started by Adam20, Aug 11, 2016.

  1. Adam20

    Adam20 MDL Novice

    Sep 6, 2007
    41
    3
    0
    Hey all,
    I wondered if any of you hackers out there would know if it is technically feasible to be able to enable the Hyper-V VSS Writer on Client Hyper-V within Windows 10?

    I ask because in the event log you see this warning under when the service starts:

    Microsoft-Windows-Hyper-V-VMMS/Admin

    Log Name: Microsoft-Windows-Hyper-V-VMMS-Admin
    Source: Microsoft-Windows-Hyper-V-VMMS
    Date: 11/08/2016 17:43:28
    Event ID: 10130
    Task Category: None
    Level: Information
    Keywords:
    User: SYSTEM
    Description:
    Hyper-V VSS is not supported on client operating systems.

    I am guessing it is doing some OS check - the process for the service is VMMS.exe and it sits within C:\Windows\System32

    Some help would be appreciated, I know there are some very clever people out there.

    Thanks
     
  2. Adam20

    Adam20 MDL Novice

    Sep 6, 2007
    41
    3
    0
    Has anybody got any ideas?

    Cheers
     
  3. vyvojar

    vyvojar MDL Novice

    Aug 10, 2016
    22
    13
    0
    Maybe. Can you run hxxps://github.com/vyvojar/poldump/releases/download/v32/pdnt.exe (compile from source if you're afraid of random binaries) on both the server and client machines, and post output? If this is a "soft limit" imposed by kernel policy, there are ways to override it...
     
  4. T-S

    T-S MDL Guru

    Dec 14, 2012
    3,988
    1,316
    120

    The policies can be edited using the product policy editor, but you need to keep the the clipservice disabled, which, in turn, leads to an unactivated copy.

    In short you would need some patched file like we did for the WMC which is affected by a similar problem

    But unlike the wmc this is a low level component, very likely you would need to disable the test signing, an the checks for integrity.

    In short anything but simple.

    If you purpose is personal is way better/quicker to use WinServer as a desktop system, Win server2016 is practically the cleanest and fastest member of the W10 family, and unlike the older versions it's practically on par with W10.

    The few missing pieces are already available (I made the Linux Subsystem package, someone else explained how to install the Store and EDGE (assuming you need them), and so on...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. vyvojar

    vyvojar MDL Novice

    Aug 10, 2016
    22
    13
    0
    Not necessarily, if you use the same approach as rdpwrap, that is, keep the policy local. The point is, which policy it is, actually?
     
  6. KNARZ

    KNARZ MDL Addicted

    Oct 9, 2012
    872
    457
    30
    #6 KNARZ, Aug 26, 2016
    Last edited by a moderator: Apr 20, 2017
    T-S
    1) clipservice can also completely manage PP or only in combination with sppsvc? - My question is, is it Independent or does it depend on between each other? You have any info?
    2) I compared Datacenter and Enterprise PP but there is non Hyper-V VSS related stuff. So I guess "only" the Package is missing this component (maybe with dependencies)

    Packages that are in Datacenter but not in Enterprise:
    Code:
    Microsoft-Hyper-V-Offline-Package 
    Microsoft-Hyper-V-Offline-vm-Package 
    Microsoft-Hyper-V-Online-Package 
    Microsoft-Hyper-V-Server-Drivers-Common-Package 
    Microsoft-Hyper-V-Server-Drivers-Common-services-Package 
    Microsoft-Hyper-V-Server-Drivers-Package 
    Microsoft-Hyper-V-Server-Drivers-services-Package 
    Microsoft-Hyper-V-ServerEdition-Package 
    
    Packages that are in Enterprise but not in Datacenter:
    Code:
    Microsoft-Hyper-V-ClientEdition-Package 
    Microsoft-Hyper-V-Services-Package 
    
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. T-S

    T-S MDL Guru

    Dec 14, 2012
    3,988
    1,316
    120
    I'm not really an expert of that, all I know is that on the older windows you had to disable the SPPservice on W10 you have to disable the ClipSVC.

    I assume the latter took the role of the former, and the former is there just for compatibility with the past
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. T-S

    T-S MDL Guru

    Dec 14, 2012
    3,988
    1,316
    120

    That's something that must be investigated. I didn't look at them lately. And BTW I'm not a coder.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. KNARZ

    KNARZ MDL Addicted

    Oct 9, 2012
    872
    457
    30
    I guess he thinks it's group policy but we mean ProductPolicy. - And as I said, there is none Hyper-V VSS related (so we can guess there is none). Just the packages are different.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. T-S

    T-S MDL Guru

    Dec 14, 2012
    3,988
    1,316
    120
    #10 T-S, Aug 26, 2016
    Last edited: Aug 26, 2016

    Anyway...

    http://forums.mydigitallife.net/thr...14393-(1607)?p=1269625&viewfull=1#post1269625

    P.S. I'm sure you would like this

    http://forums.mydigitallife.net/thr...alternatives?p=1269460&viewfull=1#post1269460

    Not the thing itself, but the method, which in theory opens to endless possibilities.

    Say Windows Home server 2012 or 2016, or the port of 2012's HyperV on Win server 2016 (to allow it on machines lacking the second level addres translations) and so on...;)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. vyvojar

    vyvojar MDL Novice

    Aug 10, 2016
    22
    13
    0
    #11 vyvojar, Aug 27, 2016
    Last edited: Aug 27, 2016
    Policy may indeed be unrelated completely, and this being a simple check for client SKU (handled by sppsvc too, but via the usual SL api).

    clipsp.sys appears to be same thing as spsys.sys from windows 7. That is, the kernel part of sppsvc, they're both the same thing more or less, just the user/kernel parts. If it behaves the same as spsys, clipsp is the one who sets policy 'tampered' bit if you mess with policies or kill its userspace sppsvc counterpart.
     
  12. Adam20

    Adam20 MDL Novice

    Sep 6, 2007
    41
    3
    0
    Sorry guys but most of this is above my head - are you saying that it should technically be possible to do this?

    I'm hessitant to run full blown Server 2016 on my main box becuase I use MediaPortal and every time it launches it does say its incompatable with Windows Server even though it does run perfectly, but if I had any issues with it further down the line unfortunately I wouldnt be able to get any help from the MediaPortal guys :-/
     
  13. Adam20

    Adam20 MDL Novice

    Sep 6, 2007
    41
    3
    0
    Bump... Anyone?
     
  14. xinso

    xinso MDL Guru

    Mar 5, 2009
    4,442
    5,569
    150
    #15 xinso, Oct 25, 2016
    Last edited by a moderator: Apr 20, 2017
    Package for Datacenter:
    Code:
    Microsoft-Hyper-V-ServerEdition-Package

    Package for Enterprise:

    Code:
    Microsoft-Hyper-V-ClientEdition-Package
    
     
  15. Adam20

    Adam20 MDL Novice

    Sep 6, 2007
    41
    3
    0
    #16 Adam20, Oct 26, 2016
    Last edited by a moderator: Apr 20, 2017
    (OP)
    Well I tried using the SXS Extractor using the two commands:


    cscript.exe sxsextract.vbs /INCLUDERES /online C:\Windows\servicing\Packages\Microsoft-Hyper-V-ServerEdition-Package~31bf3856ad364e35~amd64~~10.0.14393.0.mum D:\SXSExtractor\Microsoft-Hyper-V-ServerEdition-Package~31bf3856ad364e35~amd64~~10.0.14393.0.cab

    cscript.exe D:\SXS\sxsextract.vbs /INCLUDERES /online C:\Windows\servicing\Packages\Microsoft-Hyper-V-ServerEdition-Package~31bf3856ad364e35~amd64~en-US~10.0.14393.0.mum D:\SXSExtractor\Microsoft-Hyper-V-ServerEdition-Package~31bf3856ad364e35~amd64~en-US~10.0.14393.0.cab

    Copied the two CABS to a Windows 10 install and tried installing them with DISM, the EN-US package installs but the base package errors:

    eployment Image Servicing and Management tool
    Version: 10.0.14393.0

    Image Version: 10.0.14393.0

    Processing 1 of 1 - Adding package Microsoft-Hyper-V-ServerEdition-Package~31bf3856ad364e35~amd64~~10.0.14393.0
    [==========================100.0%==========================]
    An error occurred - Microsoft-Hyper-V-ServerEdition-Package Error: 0x800736cc

    Error: 14028

    A component's file does not match the verification information present in the component manifest.
     
  16. xinso

    xinso MDL Guru

    Mar 5, 2009
    4,442
    5,569
    150
    #17 xinso, Oct 26, 2016
    Last edited by a moderator: Apr 20, 2017
    The difference between Client and Server:
    Code:
    Client:
    Microsoft-Hyper-V-Services-Package~31bf3856ad364e35~amd64~~10.0.14393.0
    Microsoft-Windows-RemoteFX-Graphics-Virtualization-Host-Package~31bf3856ad364e35~amd64~~10.0.14393.0
    Microsoft-Windows-RemoteFX-HyperV-Integration-Package~31bf3856ad364e35~amd64~~10.0.14393.0
    Microsoft-Windows-Virtualization-RemoteFX-User-Mode-Transport-Package~31bf3856ad364e35~amd64~~10.0.14393.0
    
    Microsoft-Hyper-V-Services-Package~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0
    Microsoft-Windows-RemoteFX-Graphics-Virtualization-Host-Package-LanguagePack~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0
    Microsoft-Windows-RemoteFX-HyperV-Integration-Package-LanguagePack~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0
    Microsoft-Windows-Virtualization-RemoteFX-User-Mode-Transport-Package~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0
    
    Server:
    Microsoft-Hyper-V-Offline-Package~31bf3856ad364e35~amd64~~10.0.14393.0
    Microsoft-Hyper-V-Offline-vm-Package~31bf3856ad364e35~amd64~~10.0.14393.0
    Microsoft-Hyper-V-Online-Package~31bf3856ad364e35~amd64~~10.0.14393.0
    Microsoft-Hyper-V-Server-Drivers-Common-Package~31bf3856ad364e35~amd64~~10.0.14393.0
    Microsoft-Hyper-V-Server-Drivers-Common-services-Package~31bf3856ad364e35~amd64~~10.0.14393.0
    Microsoft-Hyper-V-Server-Drivers-Package~31bf3856ad364e35~amd64~~10.0.14393.0
    Microsoft-Hyper-V-Server-Drivers-services-Package~31bf3856ad364e35~amd64~~10.0.14393.0
    Microsoft-OneCore-NetworkController-SDNDiagnostics-Package~31bf3856ad364e35~amd64~~10.0.14393.0
    
    Microsoft-Hyper-V-Offline-Package~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0
    Microsoft-Hyper-V-Offline-vm-Package~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0
    Microsoft-Hyper-V-Online-Package~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0
    Microsoft-Hyper-V-Server-Drivers-Common-Package~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0
    Microsoft-Hyper-V-Server-Drivers-Common-services-Package~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0
    Microsoft-Hyper-V-Server-Drivers-Package~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0
    Microsoft-Hyper-V-Server-Drivers-services-Package~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0
    Microsoft-OneCore-NetworkController-SDNDiagnostics-Package~31bf3856ad364e35~amd64~xx-XX~10.0.14393.0
    But it is hard to install them for the issue you encountered.

    Server-as-Desktop is the easiest way.
    Code:
    D:\Desktop>wmic path SoftwareLicensingProduct where (PartialProductKey!=NULL) get ID,LicenseStatus,Name,PartialProductKey,ProductKeyChannel /format:list
    
    ID=2cf1c8d6-ebe1-4ce9-83c6-c4877fae1355
    LicenseStatus=1
    Name=Windows(R), ServerHyperCore edition
    PartialProductKey=KR36H
    ProductKeyChannel=Retail
    
    ID=c47456e3-265d-47b6-8ca0-c30abbd0ca36
    LicenseStatus=1
    Name=Office 16, Office16ProPlusVL_MAK edition
    PartialProductKey=QYH7M
    ProductKeyChannel=Volume:MAK
    
    ID=295b2c03-4b1c-4221-b292-1411f468bd02
    LicenseStatus=1
    Name=Office 16, Office16VisioProVL_MAK edition
    PartialProductKey=6MVCB
    ProductKeyChannel=Volume:MAK
    
     
  17. guest2free

    guest2free MDL Novice

    Dec 18, 2009
    6
    1
    0
    Hello xinso,
    as I can see in this and other threads you have managed to use Hyper-V activation for a full GUI Windows 2016 server ?
    Do you care to share how you did it ? Thanks
     
  18. Adam20

    Adam20 MDL Novice

    Sep 6, 2007
    41
    3
    0
    Something's changed in the Creators Update and Hyper-V VSS Writer now functions in Client Hyper-V just like in Windows Server which is great. Hopefully it will stay like this!
     
  19. sebus

    sebus MDL Guru

    Jul 23, 2008
    5,879
    1,773
    180
    Hopefully, as there is no logical reason NOT to have it working!