I see the support is a forum with boilerplate “replace this for your users.”
I bought the product but it hasn’t worked for me yet. Error code 60 on the last try.
Not sure I am following. Winclone is definitely active and still works great. I am a human (last I checked) and try my best to help folks out that are having issues. Can you give a me a bit more info on what the issue is?
tim
haha - ok.
Well - I have tried volume to volume and volume to image then tried restore image and haven’t yet gotten my bootcamp partition to clone.
Currently, I get a Restore Error “WIM-based restore failure error code 60”.
The KB articles seem to be for WinClone 6, but I assume they’re good for 7.
system.log provides the following mentions of WinClone:
Jun 13 09:33:53 chrismbp Winclone[777]: objc[777]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fff91ca03d8) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x1098a2f50). One of the two will be used. Which one is undefined.
Jun 13 09:33:53 chrismbp Winclone[777]: assertion failed: 18F132: libxpc.dylib + 90677 [9A0FFA79-082F-3293-BF49-63976B073B74]: 0x89
Jun 13 09:33:53 chrismbp com.apple.xpc.launchd[1] (com.getdropbox.dropbox.garcon.C18AD0AA-D4E3-4413-A9B3-7EDA848A8EA3[796]): Caller wanted oneshot behavior for pre-existing instance: caller = Winclone
Jun 13 09:33:53 chrismbp com.apple.xpc.launchd[1] (com.microsoft.OneDrive.FinderSync.D23BEE25-3F81-424B-A7AB-04EFA67D8BAA[797]): Caller wanted oneshot behavior for pre-existing instance: caller = Winclone
Jun 13 09:33:53 chrismbp com.apple.xpc.launchd[1] (com.getdropbox.dropbox.garcon.0A6C4A09-D5BD-4676-B488-A7454CA73D71[799]): Caller wanted oneshot behavior for pre-existing instance: caller = Winclone
Any ideas?
That log snippet doesn’t have much in the way of what happened. A few things to try:
-
Save the image first, then restore the image. There have been reports that this works better, though we have not been able to replicate this internally.
-
Look at the full logs by running:
ok - just tried again and got error code 60 - from log dump:
[ERROR] ++++:34:56.783898-0500 localhost com.twocanoes.WincloneHelper[660]: [com.twocanoes.winclone:WincloneHelper] +++++
2019-06-13 11:34:56.784166-0500 localhost com.twocanoes.WincloneHelper[660]: [com.twocanoes.winclone:WincloneHelper] +++++ Failed to set DOS name of “/LocalDev/hold2/APNDT/inzi.rabbit/angular/node_modules/datamaps/src/js/data/nul.json” in NTFS volume ++++
2019-06-13 11:34:56.787074-0500 localhost com.twocanoes.WincloneHelper[660]: [com.twocanoes.winclone:WincloneHelper] +++++ : Invalid argument
++++
2019-06-13 11:34:58.625287-0500 localhost com.twocanoes.WincloneHelper[660]: [com.twocanoes.winclone:WincloneHelper] +++++ ERROR: ++++
2019-06-13 11:34:58.625446-0500 localhost com.twocanoes.WincloneHelper[660]: [com.twocanoes.winclone:WincloneHelper] +++++ Exiting with error code 60:
Failed to set short name on extracted file.
++++
2019-06-13 11:34:58.774396-0500 localhost Winclone[603]: [com.twocanoes.winclone:Application] Helper tool error: WIM-based restore failure with error code 60
[ERROR] Failed to set DOS name of “/LocalDev/hold2/APNDT/inzi.rabbit/angular/node_modules/datamaps/src/js/data/nul.json” in NTFS volume: Invalid argumentandardError=
ERROR: Exiting with error code 60:
Failed to set short name on extracted file.
Verifying integrity of “/Users/chris/Dev/bootcamp_3.winclone/Windows.wim”: 0 GiB of 85 GiB (0%) done
2019-06-13 11:34:58.776640-0500 localhost Winclone[603]: (DiskDevice) Mounting /dev/disk0s3
2019-06-13 11:34:59.609111-0500 localhost Winclone[603]: (DiskDevice) Mounting /dev/disk0s3 Finished
2019-06-13 11:35:04.264538-0500 localhost Winclone[603]: (LaunchServices) 27366555: RECEIVED OUT-OF-SEQUENCE NOTIFICATION: 115 vs 132, 512,
I’m going to move some of my dev folders off my bootcamp partition - see if it’s happier.
Sounds like the best idea. Let me know how it goes.
Same here. I bought it and tried for months, on two different computers, to get it to work with no success. Finally gave up.
Trying again - have yet to get this to work.
Currently imaging my old bootcamp and see this error:
2019-06-14 14:15:15.620160-0500 localhost Winclone[806]: (LaunchServices) 27366555: RECEIVED OUT-OF-SEQUENCE NOTIFICATION: 201 vs 214, 512,
What does that mean? Does that mean this attempt is going to fail, too?
I never got Winclone 6 to work.
Now that I’m retired, rebuilding my system from scratch isn’t such an onerous task.
Failed AGAIN.
Seems it does not like things like YARN cache. sigh…
did you try switching to block based mode? This has resolved file related errors.
Hmm Everything is becoming clear now, 3 failures on disk to disk clone, one sort of success but drive doesn’t boot or show up in the boot options. waste of money and Time, more truths need to be told at the sales point.
Sorry you are having issues. Most folks have an easy time with Winclone, but given the state of some Windows installs, it can have issues. Given that, we offer a refund if it doesn’t work for you. Please submit a request at http://twocanoes.com/refunds/
tim
1 Like
Hmm, seems I jumped the gun, I had tried 3 times to clone with version 6, each time it failed, after writing my above comment I discovered I was entitled to version 7, I downloaded that and hey presto it worked first time, perfect! anyone reading this, use it. it works!
1 Like