FSRM, SMI-S, and iSCSI problems error code 2147749892

I had a problem with creating and/or importing VHDX files to iSCSI Target server.  While using Server Manager in the iSCSI wizard to create the target, the wizard would fail the following when trying to create the VHDX file.

WS-management service cannot process the request the wmi service or the wmi provider returned an unknown error 0x80041004

While looking through the events in WMI-Activity, I would see the following errors generated, even when I ran the wizard on the local host server:

Id = {B7CD9665-F333-0001-2C99-CDB733F3CF01}; ClientMachine = XXXXX; User = XXXXX\Administrator; ClientProcessId = 680; Component = Unknown; Operation = Start IWbemServices::ExecMethod - root\wmi : WT_Disk::ImportWTDisk; ResultCode = 0x80041004; PossibleCause = Unknown

or

Id = {B7CD9665-F333-0002-7497-CDB733F3CF01}; ClientMachine = XXXXX; User = XXXXX\Administrator; ClientProcessId = 452; Component = Unknown; Operation = Start IWbemServices::ExecMethod - root\wmi : WT_Disk::CreateVhdWTDisk; ResultCode = 0x80041004; PossibleCause = Unknown

Within Server Manager, the event reported would be:

The Microsoft iSCSI Target Server service could not create the virtual disk using device V:\iscsivirtualdisks\testvhd.vhdx. The operation failed with error code 2147749892.

I could not create or import any VHDX files using the wizard at all.  I had no problems creating them using DISKPART or even through using the Disk Management.

To attempt to resolve the issue, I removed the following patches:

KB2995388
KB3000061

I then proceeded to remove the following Roles:

File Server Resource Manager (FSRM)
Windows Standard-Based Storage Management (SMI-S)

I re-applied KB2995388 and did "not" install KB3000061, and now the wizard works perfectly and there are no more errors generated in WMI-Activity.  Something either with those roles or in KB3000061 is causing a problem with WT_Disk::CreateVhdWTDisk and WT_Disk::ImportWTDisk...

I worked on this for two days to try to get it back online (which it is now), and am quite afraid to try re-adding KB3000061 or those other roles again until I know for certain what the cause is.

any insight would be really helpful!