I wanted to update BOINC from 7.8.2 to 7.8.3.
I noticed that BOINC with VM has an older VM Box so I installed VM box 5.2 and downloaded the BOINC install without the VM Box.
So now I am trying to install BOINC 7.8.3 but the installation stops with the following error:
---
Error 1923.Service BOINC (BOINC) could not be
installed. Verify that you have sufficient privileges to
install system services.
[ Abort ] [ Retry ] [ Ignore ]
---

can anybody shed some light on how to set my system services privileges?

I'm guessing this is on Windows: which version of Windows? And if Windows 10, which build or sub-version?

Have you tried right-clicking on the installer file in your download directory, and selecting 'Run as Administrator' from the context menu?

Edit - if this is a Windows Server, specifically a Domain Controller (so Small Business Server and up), you may find that installing 'as as service' is impossible. We used not to allow the installer to run at all: now that restriction has been lifted, but Microsoft still doesn't allow our installer to create system services on a domain controller. So BOINC can only be installed in User mode on DCs - hardly ideal, but better then nothing.

Thanks Richard,

Yes, Win7 home. and I kept clicking the install for about 4 or 5 times, even tried "run as admin" to no avail and always returning the same error, so I simply gave up and waited for a reply to my message. (well, I did one more try with clicking on [ Ignore ] instead on cancel, and BOINC client just said "no BOINC server")

...and here I am now, dumbfounded, having clicked on the installer after reading your message, and the install wizard said "do you want to repair or uninstall BOINC", so I figure repair is the way to go...

...and now BOINC is crunching away again...

I guess whatever was blocking BOINC had to have time to unblock (my clicking on ignore probably didn't help much -- or did the trick without me realizing it) and the repair finalized the installation, because now I see:
10/26/2017 16:01:40 | | Starting BOINC client version 7.8.3 for windows_x86_64
10/26/2017 16:01:40 | | log flags: file_xfer, sched_ops, task
10/26/2017 16:01:40 | | Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8
10/26/2017 16:01:40 | | Running as a daemon (GPU computing disabled)
10/26/2017 16:01:40 | | Data directory: C:\ProgramData\BOINC
10/26/2017 16:01:40 | | Running under account boinc_master
10/26/2017 16:01:40 | | No usable GPUs found
10/26/2017 16:01:40 | | Version change (7.8.2 -> 7.8.3)
10/26/2017 16:01:41 | | Host name: ROBI-NB
10/26/2017 16:01:41 | | Processor: 4 GenuineIntel Intel(R) Core(TM) i5 CPU M 460 @ 2.53GHz [Family 6 Model 37 Stepping 5]
10/26/2017 16:01:41 | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 cx16 sse4_1 sse4_2 popcnt syscall nx lm vmx tm2 pbe
10/26/2017 16:01:41 | | OS: Microsoft Windows 7: Home Premium x64 Edition, Service Pack 1, (06.01.7601.00)
10/26/2017 16:01:41 | | Memory: 3.79 GB physical, 7.69 GB virtual
10/26/2017 16:01:41 | | Disk: 576.64 GB total, 203.71 GB free
10/26/2017 16:01:41 | | Local time is UTC -5 hours
10/26/2017 16:01:41 | | VirtualBox version: 5.2.0

So the VM Box is discovered correctly with its new version as well :)

Again, thanks for your ideas and thoughts

Yes, there are many ways to fix a broken computer. Among them are:

* Go and have a nice cup of tea, and try again later.

* Switch it off and switch it on again.

* Have a long sulk - preferably overnight - and try again in the morning.

* Spend hours explaining your problem to somebody else, even if they aren't listening.

I'm glad at least one of them worked for you ;-)

I have found that Defenfer will hold files (presumably to scan them) and the simple solution of waiting a few minutes and trying again usually works. Its particularly noticeable on larger files like installers.

---

MarkJ