Author Topic: The ScRegSetValueExW call failed for Start  (Read 37940 times)

0 Members and 1 Guest are viewing this topic.

Offline DavidR

  • Avast √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 88464
  • No support PMs thanks
Re: The ScRegSetValueExW call failed for Start
« Reply #15 on: November 27, 2008, 11:36:00 PM »
OK we will have to wait for more input from Vlk.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 23.10.6086 (build 23.10.8563.800) UI 1.0.784/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

chetola

  • Guest
Re: The ScRegSetValueExW call failed for Start
« Reply #16 on: November 28, 2008, 02:10:10 PM »

No errors since the latest update, yesterday.

Thanks to all for the help.

Avast is a great program and the forum just makes it better.

David

Offline DavidR

  • Avast √úberevangelist
  • Certainly Bot
  • *****
  • Posts: 88464
  • No support PMs thanks
Re: The ScRegSetValueExW call failed for Start
« Reply #17 on: November 28, 2008, 02:38:36 PM »
Good news, thanks for the update.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 23.10.6086 (build 23.10.8563.800) UI 1.0.784/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

JeffChao284

  • Guest
Re: The ScRegSetValueExW call failed for Start
« Reply #18 on: March 02, 2013, 05:18:09 PM »
Since the last Avast update I have received this error message{4 in a row in the event viewer}:

The ScRegSetValueExW call failed for Start with the following error:
Access is denied.

Does anyone know why?

Thanks,
David

Well I wanted to make an update to the latest version of this program that was noted, apparently I did not know that Avast has no way of changeing the service Cedentionals to where you are not allowed to set it on Manual or Disabled, but an odd error has come up,

ScRegSetValueExW error when changing the Service ot either Manual or Disabled causes this same error, worse, it also cause a Corruption in the Event Viewer System Log and it even disables the user from getting into the Services Consule which is not normal of Avast and might need to be looked at, although I doubt you would understand this or even help anyone who is still on Windows 2000 SP4, but this is a bug that is well not been checked...