I have a Windows Service that I'm having this issue with.
Version : v4.0.30319
CLR Header: 2.5
PE : PE32+
CorFlags : 0x1
ILONLY : 1
32BITREQ : 0
32BITPREF : 0
Signed : 0
I even tried running Corflags with the 32BITREQ-
and 32BITPREF-
flags to make sure it was set to what it's supposed to be but no dice. In the taskManager it shows up as:
MyServiceName (32 bit)
Service was installed with Topshelf 3.0 and is running on Windows Server 2012 R2 Standard. What's going on here?
I had this issue when a previous version of the service had been 32 bit. I knew the currently installed one wasn't (checked CORFLAGS), but the process associated with the service was being created as 32 bit anyway, and for the life of me I couldn't work out why.
After a reboot the problem went away. I wonder if the Service Control Manager 'remembers' the bitness for each service, as a startup optimization (or something).
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With