Windows 10: MSMQ

I have a windows computer app that requires MSMQ to be installed/enabled. Normally you would go to programs and features and the turn windows features on or off to turn MSMQ on. A random selection of computers on my network have this feature available. This computer is windows 10, version 1803, build 17134.1. MSMQ is not available. Can anyone help out here? Reloading the computer is not an option.

:)

 

Unable to turn on MSMQ on Windows 10 Pro

Hi,

I am a developer and I want to do some project work using MSMQ. Currently I am using Windows 10 Pro in my personal PC.

I tried to turn on the MSMQ feature from control panel (Control Panel > Turn Windows feature on or off > MSMQ)

But every time it is giving me an error with error code 0x800F0922. I google it and could not find any solution for Windows 10. Please find the below screenshot. Please help me resolve this issue.

 

Running MSMQ using vb.net on remote Win10 workstations in a workgroup.


I am trying to run MSMQ sending messages from one Win10 workstations to a remote Win10 workstation within the same workgroup. I don't have a server or a domain. I am writing using VB.net. I have no problems running local private queues on a single machine. No luck trying to send to a remote queue.
The only samples are either written in VB 6.0 or reference local queues.
There are references that it can be done without a server/domain but all reference libraries in VB 6.0.

Any help, sample code, links to solutions would be appreciated.

 

Volume Shadow Copy Service error: Unexpected error

Windows 10 x 64 Event Log shows following error

//

Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Toegang geweigerd. (=accessed denied)

. This is often caused by incorrect security settings in either the writer or requestor process.

Bewerking:

Schrijvergegevens verzamelen (=gathering writer data)

Context:

Klasse-id van schrijver: {e8132975-6f93-4464-a53e-1050253ae220} (=writer class id)

Naam van schrijver: System Writer (=writer name)

Instantie-id van schrijver: {b65f652c-6114-48fc-829c-977f40e6df77} (=writer instance id)

//

(note: this is windows 10 x64 dutch, with English language pack, often translations are 'so-so')

solution: run services.msc, select volume shadow copy, set to start + automatically = apply

However . . .

Question: how to detect what caused VSS to be set to 'manual' in first instance?

The only other entry in Event Log -source 'VSS' is:

Volume Shadow Copy Service: Writer with name MSMQ Writer (MSMQ) and ID {7e47b561-971a-46e6-96b9-696eeaa53b2a} attempted to subscribe during setup.

Bewerking:

Schrijver initialiseren (initiliaze writer, or something)

Context:

Klasse-id van schrijver: {7e47b561-971a-46e6-96b9-696eeaa53b2a}

Naam van schrijver: MSMQ Writer (MSMQ)

Instantienaam van schrijver: MSMQ Writer (MSMQ)

=

Thanks

=