Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - pol098

Pages: [1]
I don't seem to be able to add to previous threads; this relates to existing threads,4281.msg32230.html#msg32230 Registry Backup crashing
and,4514.msg33092.html#msg33092 Registry backup crashes Win10, auto mode. MSVBVM60.DLL bug

The problem: automatic registry backup (5 minutes after booting) doesn't work. See the other threads for details. Manual backup seems to work fine,

I've just received a private message "Has there been a fix?". This is a response; unlike my earlier posts I'm replying from fading memory of what I did next, so not totally reliable. I haven't retested recently, but I'm not particularly hopeful. My opinion has changed somewhat; while the error messages about MSVBVM60.DLL were real, I don't think that they relate to this problem, but are a harmless error that doesn't actually affect registry backup. My best guess is that it is something to do with permissions. I'm backing up to a a data drive (D:); as far as I remember, automatic backup to the system drive (C:) did work, but I don't want to do that. The obvious answer is a permissions problem, but giving unrestricted access to the specified backup directory did not help.

This is just a response to the question received; I haven't actively done anything at all since the earlier thread, and make manual registry backups. I think I tested the current release of Registry Backup (released quite a while ago) for automatic operation, without success, but am not sure. HTH

Added 1Dec17: I've quite often found that various problems that couldn't be solved eventually go away, due presumably to updating of operating systems, drivers, etc. As this old problem has just been reported to me in a personal message, I'd guess that it's still there today. Windows 10 is more or less guaranteed to be up-to-date for everyone. The problem occurs when using Windows Task Scheduler; maybe it could be worked around by using a third-party scheduling program (the old Windows "at" command and its replacement "schtasks" use the Task Scheduler service)?

Re: Tweaking Registry Backup crashing, MSVBVM60.DLL faults

I'm repeating something I posted in an existing thread last month.,4281.msg32230.html#msg32230 ,
just in case it got missed there (although I had some responses).

I've been having a problem that others have reported (search the forum for MSVBVM60) with Registry Backup. I had been using ERUNT, successfully, under Win 7 (it didn't back up the Components hive, but I was OK without it), but it didn't behave well under Win 10 so I installed RB. Win 10/64, up-to-date as of now, current RB As it wasn't working I changed the VSS executable from automatic to vss_7_8_2008_2012_64.exe, same behaviour.

I have set up RB to run as System on login of any user, saving to a non-standard location and not more than once per day. The VSS service was initially set to run manually, but I changed it to automatic. RB runs fine manually, but does not back up automatically. I looked at the event log and found Error, event ID 1000. Details:

Faulting application name: TweakingRegistryBackup.exe, version:, time stamp: 0x56f4a2b2
Faulting module name: MSVBVM60.DLL, version:, time stamp: 0x49b01fc3
Exception code: 0xc0000005
Fault offset: 0x000c9ba6
Faulting process id: 0x2040
Faulting application start time: 0x01d19a3622cb4882
Faulting application path: C:\Program Files (x86)\\Registry Backup\TweakingRegistryBackup.exe
Faulting module path: C:\WINDOWS\SYSTEM32\MSVBVM60.DLL
Report Id: 6b50db5c-33de-48da-9eb6-f3e412c3c5d8
Faulting package full name:
Faulting package-relative application ID:

MSVBVM60.DLL is a Visual Basic Virtual Machine. On running manually a shadow copy is created, with a progress indicator; the automatic invocation doesn't seem to have created a shadow copy. It doesn't seem to be a timing issue, with the VSS service not being ready at login time: RegisrtyBackup be default sets up Task Scheduler to delay 5' after login. I don't know if Microsoft provide debugging maps and so on to pin down the MSVBVM60.DLL error.

My machine is a modern laptop sold as suitable for games, has 8GB of RAM and a 4-core 2.5GHz Intel i7 CPU, though using Intel 4600 on-chip graphics instead of a high-performance card, and the backup works perfectly if started manually, so I don't think performance is an issue.

This may well be a program problem that needs addressing; I'm not the only one to report this issue (see )
Does RB make any calls to the Visual Basic Virtual Machine DLL MSVBVM60.DLL in automatic mode that it doesn't make in manual mode? The Event Viewer error message gives a specific exception 0xc0000005 - an access violation - in that module, at 0x000c9ba6.

ADDED LATER: there are many reports of problems and crashes with MSVBVM60.DLL (plus a lot of rubbish sites found by Google). One suggested action that was reported to work for some, but not all, people in 2010 (pre-Win10) was to use an earlier MSVBVM60.DLL from WinXP. I haven't yet followed this up. All the versions of this file that I've found, back to Win98, seem to be about the same size (rounding to 1.32MB), so maybe it hasn't been changed much.

I can't comment on the Registry Backup program and haven't yet tried to restore a backup; if it ultimately works as well as ERUNT did under Win7 I'll be happy. A suggestion I'd make is an option to use "20160510" (or 160510) in file/directory names instead of "10May16", as this form sorts alphanumerically in chronological order. I set ERUNT up to iuse this (not the default), and it's helpful.

Best wishes, pol098

Pages: [1]