Jump to content
Covecube Inc.

JazJon

Members
  • Content Count

    53
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by JazJon

  1. I wanted to report that today's 2.2.2.934 install was the first build that didn't hang a long time before the install completed. It was a normal amount of install time. :)
  2. I just installed a recent BIOS update for my ASUS motherboard. https://www.asus.com/us/Motherboards/PRIME-H270-PRO/HelpDesk_BIOS/ Version 1006 2018/03/308.11 MBytes PRIME H270-PRO BIOS 1006 1. Update CPU Microcode 2. Improve system security and stability File Explorer open zippier + populates my listed drives much faster. The system seems overall more stable. Installers are still hanging though, hmmmm Might have something to do with System Restore as you said before. I'll try to disable that. I usually leave it disabled, but I've regretted not being able to restore to a known good state a few times too. (damned if you do damned if you don't)
  3. Success! (just had to wait a very long time) [5738:4FC0][2018-03-14T14:25:21]i319: Applied execute package: DrivePoolApplication, result: 0x0, restart: Required [0B28:0B4C][2018-03-14T14:25:21]i325: Registering dependency: {9566583d-5ece-4d50-9cb7-0f19e9cfc438} on package provider: {43053F4F-87D0-4459-A600-03896AC6F486}, package: DrivePoolApplication [0B28:0B4C][2018-03-14T14:25:21]i301: Applying execute package: {64f610f6-b3ce-44e9-acef-48e96db0bb94}, action: Uninstall, path: C:\ProgramData\Package Cache\{64f610f6-b3ce-44e9-acef-48e96db0bb94}\StableBit.DrivePool_x64.exe, arguments: '"C:\ProgramData\Package Cache\{64f610f6-b3ce-44e9-acef-48e96db0bb94}\StableBit.DrivePool_x64.exe" -uninstall -quiet -burn.related.upgrade -burn.ancestors={9566583d-5ece-4d50-9cb7-0f19e9cfc438} -burn.filehandle.self=936' [5738:4FC0][2018-03-14T14:25:21]i319: Applied execute package: {64f610f6-b3ce-44e9-acef-48e96db0bb94}, result: 0x0, restart: None [0B28:0B4C][2018-03-14T14:25:21]i372: Session end, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{9566583d-5ece-4d50-9cb7-0f19e9cfc438}, resume: ARP, restart: Required, disable resume: No [0B28:0B4C][2018-03-14T14:25:21]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{9566583d-5ece-4d50-9cb7-0f19e9cfc438}, resume: ARP, restart initiated: No, disable resume: No [5738:4FC0][2018-03-14T14:25:22]i399: Apply complete, result: 0x0, restart: Required, ba requested restart: No
  4. Ok I kept waiting and it just got a bit further. (now stuck on Processing) Continuation of logs.......... 0B28:0B4C][2018-03-14T14:19:07]i361: Created a system restore point. [0B28:0B4C][2018-03-14T14:19:07]i370: Session begin, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{9566583d-5ece-4d50-9cb7-0f19e9cfc438}, options: 0x7, disable resume: No [0B28:0B4C][2018-03-14T14:19:07]i000: Caching bundle from: 'C:\Users\jon\AppData\Local\Temp\{D96890C9-8388-4891-A300-2E86A00B51C7}\.be\StableBit.DrivePool_x64.exe' to: 'C:\ProgramData\Package Cache\{9566583d-5ece-4d50-9cb7-0f19e9cfc438}\StableBit.DrivePool_x64.exe' [0B28:0B4C][2018-03-14T14:19:07]i320: Registering bundle dependency provider: {9566583d-5ece-4d50-9cb7-0f19e9cfc438}, version: 2.2.906.0 [0B28:0B4C][2018-03-14T14:19:07]i371: Updating session, registration key: SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{9566583d-5ece-4d50-9cb7-0f19e9cfc438}, resume: Active, restart initiated: No, disable resume: No [0B28:1448][2018-03-14T14:19:07]i305: Verified acquired payload: DrivePoolApplication at path: C:\ProgramData\Package Cache\.unverified\DrivePoolApplication, moving to: C:\ProgramData\Package Cache\{43053F4F-87D0-4459-A600-03896AC6F486}v2.2.906\StableBit.DrivePool.msi. [0B28:0B4C][2018-03-14T14:19:07]i323: Registering package dependency provider: {43053F4F-87D0-4459-A600-03896AC6F486}, version: 2.2.906, package: DrivePoolApplication [0B28:0B4C][2018-03-14T14:19:07]i301: Applying execute package: DrivePoolApplication, action: MinorUpgrade, path: C:\ProgramData\Package Cache\{43053F4F-87D0-4459-A600-03896AC6F486}v2.2.906\StableBit.DrivePool.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" LAUNCHUI="1" INSTALLLOCATION="C:\Program Files\StableBit\DrivePool\"'
  5. Still hung at Intializing... Here is StableBit_DrivePool_(64_bit)_20180314132902.log (3/14/2018 1:29PM) [5738:4FC0][2018-03-14T13:29:02]i001: Burn v3.11.0.1701, Windows v10.0 (Build 16299: Service Pack 0), path: C:\Users\jon\AppData\Local\Temp\{D4B60518-FDF8-4457-BE1D-901C3BDB2F03}\.cr\StableBit.DrivePool_2.2.0.906_x64_Release.exe [5738:4FC0][2018-03-14T13:29:02]i000: Initializing string variable 'InstallFolder' to value '[PlatformProgramFilesFolder]\StableBit\DrivePool' [5738:4FC0][2018-03-14T13:29:02]i000: Initializing numeric variable 'LaunchUI' to value '1' [5738:4FC0][2018-03-14T13:29:02]i009: Command Line: '-burn.clean.room=C:\Users\jon\AppData\Local\Temp\14303d3e-cf21-4cfe-ae02-0ac7654f1a34\StableBit.DrivePool_2.2.0.906_x64_Release.exe -burn.filehandle.attached=636 -burn.filehandle.self=632' [5738:4FC0][2018-03-14T13:29:02]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\jon\AppData\Local\Temp\14303d3e-cf21-4cfe-ae02-0ac7654f1a34\StableBit.DrivePool_2.2.0.906_x64_Release.exe' [5738:4FC0][2018-03-14T13:29:02]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Users\jon\AppData\Local\Temp\14303d3e-cf21-4cfe-ae02-0ac7654f1a34\' [5738:4FC0][2018-03-14T13:29:02]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\jon\AppData\Local\Temp\StableBit_DrivePool_(64_bit)_20180314132902.log' [5738:4FC0][2018-03-14T13:29:02]i000: Setting string variable 'WixBundleName' to value 'StableBit DrivePool (64 bit)' [5738:4FC0][2018-03-14T13:29:02]i000: Setting string variable 'WixBundleManufacturer' to value 'Covecube Inc.' [5738:2DDC][2018-03-14T13:29:02]i000: Setting numeric variable 'WixStdBALanguageId' to value 1033 [5738:2DDC][2018-03-14T13:29:02]i000: Setting version variable 'WixBundleFileVersion' to value '2.2.906.0' [5738:4FC0][2018-03-14T13:29:02]i100: Detect begin, 2 packages [5738:4FC0][2018-03-14T13:29:02]i000: Setting string variable 'NETFRAMEWORK45' to value '461308' [5738:4FC0][2018-03-14T13:29:02]i052: Condition 'NOT VersionNT64' evaluates to false. [5738:4FC0][2018-03-14T13:29:02]i052: Condition 'VersionNT64' evaluates to true. [5738:4FC0][2018-03-14T13:29:02]i000: Setting string variable 'PlatformProgramFilesFolder' to value 'C:\Program Files' [5738:4FC0][2018-03-14T13:29:02]i000: Setting string variable 'PreviousInstallFolder' to value 'C:\Program Files\StableBit\DrivePool\' [5738:4FC0][2018-03-14T13:29:02]i052: Condition 'PreviousInstallFolder' evaluates to true. [5738:4FC0][2018-03-14T13:29:02]i000: Setting string variable 'InstallFolder' to value 'C:\Program Files\StableBit\DrivePool\' [5738:4FC0][2018-03-14T13:29:02]i000: Setting version variable 'KmdfVersion' to value '1.23.16299.15' [5738:4FC0][2018-03-14T13:29:02]i000: Product or related product not found: {1AB7D699-E19A-45E6-992C-2FB2DC1730C7} [5738:4FC0][2018-03-14T13:29:02]i000: Setting version variable 'DrivePool1Version' to value '0.0.0.0' [5738:4FC0][2018-03-14T13:29:02]i102: Detected related bundle: {64f610f6-b3ce-44e9-acef-48e96db0bb94}, type: Upgrade, scope: PerMachine, version: 2.2.900.0, operation: MajorUpgrade [5738:4FC0][2018-03-14T13:29:02]i052: Condition 'NETFRAMEWORK45 >= 378675' evaluates to true. [5738:4FC0][2018-03-14T13:29:02]i103: Detected related package: {43053F4F-87D0-4459-A600-03896AC6F486}, scope: PerMachine, version: 2.2.900.0, language: 1033 operation: MinorUpdate [5738:4FC0][2018-03-14T13:29:02]i101: Detected package: NetFx451Web, state: Present, cached: None [5738:4FC0][2018-03-14T13:29:02]i101: Detected package: DrivePoolApplication, state: Present, cached: None [5738:4FC0][2018-03-14T13:29:02]i052: Condition '(VersionNT >= v6.0)' evaluates to true. [5738:4FC0][2018-03-14T13:29:02]i052: Condition '(KmdfVersion >= v1.9)' evaluates to true. [5738:4FC0][2018-03-14T13:29:02]i052: Condition 'DrivePool1Version = v0.0' evaluates to true. [5738:4FC0][2018-03-14T13:29:02]i199: Detect complete, result: 0x0 [5738:2DDC][2018-03-14T13:29:05]i000: Setting numeric variable 'EulaAcceptCheckbox' to value 1 [5738:4FC0][2018-03-14T13:29:05]i200: Plan begin, 2 packages, action: Install [5738:4FC0][2018-03-14T13:29:05]w321: Skipping dependency registration on package with no dependency providers: NetFx451Web [5738:4FC0][2018-03-14T13:29:05]i000: Setting string variable 'WixBundleLog_DrivePoolApplication' to value 'C:\Users\jon\AppData\Local\Temp\StableBit_DrivePool_(64_bit)_20180314132902_000_DrivePoolApplication.log' [5738:4FC0][2018-03-14T13:29:05]i201: Planned package: NetFx451Web, state: Present, default requested: Present, ba requested: Present, execute: None, rollback: None, cache: No, uncache: No, dependency: None [5738:4FC0][2018-03-14T13:29:05]i201: Planned package: DrivePoolApplication, state: Present, default requested: Present, ba requested: Present, execute: MinorUpgrade, rollback: None, cache: Yes, uncache: No, dependency: Register [5738:4FC0][2018-03-14T13:29:05]i207: Planned related bundle: {64f610f6-b3ce-44e9-acef-48e96db0bb94}, type: Upgrade, default requested: Absent, ba requested: Absent, execute: Uninstall, rollback: Install, dependency: None [5738:4FC0][2018-03-14T13:29:05]i299: Plan complete, result: 0x0 [5738:4FC0][2018-03-14T13:29:05]i300: Apply begin [5738:4FC0][2018-03-14T13:29:05]i010: Launching elevated engine process. [5738:4FC0][2018-03-14T13:29:07]i011: Launched elevated engine process. [5738:4FC0][2018-03-14T13:29:08]i012: Connected to elevated engine. [0B28:0B4C][2018-03-14T13:29:08]i358: Pausing automatic updates. [0B28:0B4C][2018-03-14T13:29:08]i359: Paused automatic updates. [0B28:0B4C][2018-03-14T13:29:08]i360: Creating a system restore point.
  6. Today (14MAR2018) I got notified via system tray about the new 2.2.0.906 update. I clicked download and install. It won't install so far. It's stuck at : Processing Initializing... I remember a previous update taking an unusual amount of time to install so I'll just leave it sit awhile before giving up. Is there anything I can do to to help see what exactly is holding up the install real time as it happens here since this seems to be a regularly occurring thing lately with new updates?
  7. I received a response from CrashPlan: "Hello Jon, Thank you for contacting our Champion Support Team. It looks like the CrashPlan app is restarting your backup unexpectedly, it is actually running a file verification scan. The scan puts ALL of your data in the To Do list. Then as the backup after the scan runs, its analyzes your files to determine if it has been backed up before and can be skipped, or if its new/changed and needs to be backed up. The percentage complete that you see is CrashPlan's progress through the current To Do list, not the overall backup. The scan is an important and normal part of CrashPlan's scheduled activities, but it can also be triggered by several events. To read more, click on the link below: http://support.code42.com/CrashPlan/Latest/Troubleshooting/Is_My_Backup_Starting_Over The explanation for the lengthy time estimation relates to how CrashPlan prioritizes files for backup. CrashPlan backs up your most recent changes first. When the scan finds new files for backup, these files go straight to the top of CrashPlan's “to do” list. This impacts the estimated time to complete backup because the estimate is based on the type of files the scan is reviewing (i.e., new or existing) and your current network speed. If you have any further CrashPlan questions or concerns, or need clarification please do not hesitate to reach out. Best Regards, Champion Support Specialist" This seems to be the case. The number of files sent match up but the total percentage is still off even after a FULL manual file scan. (that normally only happens every 30 days) Things should sort themselves out over time after the complete verification "To Do" list is done.
  8. Maybe it's because I only set the crashplan scan files schedule to every 30 days. I'm going to force a fresh scan (which takes forever) and see if it picks up things have already been backed up. (scanning in progress now)
  9. Uh oh, it seems that resetting permissions on my whole drive pool made EVERY single file I have appear to be totally new for CrashPlan. Shouldn't they be smart enough to know not to re-upload the whole file again? If I were to open a support ticket with crashplan what should I ask or tell them exactly to learn more or submit a feature request? It took a year to complete the backup last time.
  10. This thread fixed me up for permissions issues:
  11. Thanks, That fixed it. You might want to enhance your instructions to include that here. (unless maybe I missed a step) http://wiki.covecube.com/StableBit_DrivePool_Q5510455
  12. I have a follow up question. I reset permissions for the WHOLE pool as I said I was going to do. When ever I try to save a PDF file to the pool I get this: (yes my dropbox folder is on the pool, but that folder is set not to duplicate) I have to save it to my desktop (which isn't part of the pool) When I try to MOVE the .pdf file to a folder on the pool I then get: When I click Continue it works. I have this type of similar behavior trying to save a file from a app to the pool. Suggestions? Here are the properties of another folder I tried to save a different PDF to tonight
  13. Ah, I think I probably only waited 5-8 minutes max. I remember even with the drives unplugged it took awhile for the install to complete. Ok installation logs sent to 3405. (nice slick troubleshooter app!)
  14. Thanks that was easy enough just a permissions thing. (Folder Deleted!) I'm going to follow the directions to take control of the WHOLE pool to flush out left over funky permissions too.
  15. I've had a rouge folder I can't delete for a few years now. I've been meaning to post about it for a while. I've reinstalled Windows 10 and upgraded motherboards/CPU's since it's first been around. It seems to follow the pool though forever stuck. Suggestions?
  16. I wasn't able to get 2.2.0.900 to install. It hung at: I powered down, unplugged all drivepool drives. Powered up, and was able to complete the install. All is well again. I was running a nightly build from the time we had the BSoD issue fixed (after the big Windows 10 Creative update) end of last year.
  17. 2nd (solved) update. I was wrong. The problem is 2 of 5, 8tb hard drives. I plugged one 8tb drive in at a time and identified 2 that cause the Windows Installer freeze from any .MSI install or uninstall. Add any of the 2 bad drives alone or with other good ones and the new app install freeze problem happens Plugging in the three good ones together at once also resulted in normal install and uninstalls. It has to due to the fact These two drives were factory fresh initialized on my previous motherboard with a different SATA controller I think. I had a similar issue in the past when I switched hard hard drives from an external quad USB 3.0 storage box to internal SATA connectors connections. In that instance I remember moving the data off one drive at a time reinitializing the disk from scratch and then everything worked normal again. Fixed slow boot up I’m 99% sure this will be the same situation so I ordered a few new 12TB WD Gold Drives
  18. I created a new windows profile with admin rights. Logged into the new profile. MSI installers are working again! Boom, FIXED! (must have some strange corrupted windows profile)
  19. Just tried all this, no luck https://support.microsoft.com/en-au/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system
  20. Start, Run, CMD, MSIExec Shows this: (Windows Installer seems normal) I tried this to identify Windows Installer issues. (nothing found) https://support.microsoft.com/en-us/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed I'm still not sure what to do. I even rebooted in SAFE MODE and ran an app called SafeMSI that enables Windows Installer http://download.cnet.com/SafeMSI-exe/3000-2094_4-75724774.html Any Windows installation package that requires Windows Installer HANGS.
  21. Ok so I tried to update AirServer, it too get's stuck right when the install begins. What's the best way to troubleshoot stuck installers from moving forward? There has to be one common last thing being checked or something that's hanging the install package from moving forward. Thoughts/Suggestions? About an hour or so later
  22. EDIT: SOLVED I created a new windows profile with admin rights. Logged into the new profile. MSI installers are working again! Boom, FIXED! (must have some strange corrupted windows profile) _______________ EDIT 2 !!!!!!!!!!!! 2nd (re-solved) update. I was wrong. The problem is 2 of 5, 8tb hard drives. I plugged one 8tb drive in at a time and identified 2 that cause the Windows Installer freeze from any .MSI install or uninstall. Add any of the 2 bad drives alone or with other good ones and the new app install freeze problem happens Plugging in the three good ones together at once also resulted in normal install and uninstalls. It has to due to the fact These two drives were factory fresh initialized on my previous motherboard with a different SATA controller I think. I had a similar issue in the past when I switched hard hard drives from an external quad USB 3.0 storage box to internal SATA connectors connections. In that instance I remember moving the data off one drive at a time reinitializing the disk from scratch and then everything worked normal again. Fixed slow boot up I’m 99% sure this will be the same situation so I ordered a few new 12TB WD Gold Drives Original Problem ____________________________________________ I've been on DrivePool Version 2.2.0.877 Beta for a while. It fixed the problem discussed here: I saw DrivePool Version 2.2.0.881 was available so I downloaded it, and tried to install. It's stuck on Setup Progress Processing: Initializing... I rebooted and tried again. Got the same thing so let it sit 30 minutes. (no change) I rebooted, ended task on every single thing I could, tried the install again. Same thing Setup Progress Processing: Initializing... What's a good way to troubleshoot next on whats clogging up Windows 10? (latest updates) What's another good test program to install to see if the actual installer service (or whatever it's called) is broken for installing any new program? (to rule out drivepool package)
  23. Ah that's a good obvious idea for next time. My huge tower case is a tight fit between the wall and my desk so not easy to open up very fast though. (but you do what you have to do, and I'll try that instead for future similar issues) I'll also be careful not to rush any "major" Windows upgrades before checking drivepool updates are ready to rock. I'm always on the latest beta but this fresh beta build was unreleased as you said.
  24. I'm still using the same Case/Power supply but I've since upgraded to a new Motherboard/CPU/RAM/Graphics card. (and new 8TB Red Drives) The reason I upgraded was because of random Blue Screen of Death reboots. After I upgraded nearly everything I STILL had frandom BSoD issues! Long story short, it ended up being a BAD DisplayPort Cable! New DisplayPort cable, and all problems went away. (expensive troubleshooting!) Here's the "good" cable https://www.amazon.com/gp/product/B00YOP0T7G/ Intel Core i7-7700K 4.2 GHz Quad-Core LGA 1151 Processor Ballistix Sport LT 32GB Kit (16GBx2) DDR4 2400 MT/s (PC4-19200) DIMM 288-Pin - BLS2K16G4D240FSE (Red) ASUS Prime H270-PRO LGA 1151 ATX Motherboard ASUS GeForce GTX 1070 8GB ROG STRIX Graphic Card (STRIX-GTX1070-8G-GAMING)
×
×
  • Create New...