"Disc copy protection could not be verified."

i get this error when i am playing commercially bought DVDs! it aint happening on all of em, really random ones.
The disc will mount fine and will give me the option to play from start or most recent point (as usual) but then if i click either option i get:
"Disc copy protection could not be verified. The disc can not be played. (-70025)"
anyone encountered this before?

there are more users with that problem:
http://discussions.apple.com/thread.jspa?messageID=6203213&#6203213
Another one. That happened to me before the Apple Store replaced my superdrive:
http://discussions.apple.com/thread.jspa?messageID=6077903&#6077903
There are not two wihout a three:
http://discussions.apple.com/thread.jspa?messageID=6320531&#6320531
But i get no answer from Apple. They replaced my Superdrive. Then, i reinstalled MacOs, and i still can't play most of my dvds.

Similar Messages

The disc copy protection could not be verified [-70025] macbook dvd error

Hi all,
I've a 3 month old macbook but for some reason it's unable to play any genuine, retail dvds. I just get this error message: the disc copy protection could not be verified [-70025]. Front Row just quits and VLC is unpredictable.
Ironically, backup dvds of the same films work fine. Ive tried reseting the vmc and pram, reinstalling tiger then leopard from fresh installs and getting all necessary software updates. Nothing. Could this be the dreaded firmware superdrive update?
Any advice/help would be much appreciated

there are more users with that problem:
http://discussions.apple.com/thread.jspa?messageID=6203213&#6203213
Another one. That happened to me before the Apple Store replaced my superdrive:
http://discussions.apple.com/thread.jspa?messageID=6077903&#6077903
There are not two wihout a three:
http://discussions.apple.com/thread.jspa?messageID=6320531&#6320531
But i get no answer from Apple. They replaced my Superdrive. Then, i reinstalled MacOs, and i still can't play most of my dvds.

"This disc could not be verified" error when burning CDs

Every time I try to run the CD Burner, the disk seems to finalize then I get this error message:
*This disc could not be verified and might be unreliable. Try again using a new, blank disc. (Error code 0x80020063).*
I have tried with many blank disks and different data (text files, music files, etc). The CDs I am using are blank Memorex CD-RWs.
This machine is using a Matshita DVD-R UJ-845, here's the rest of the info from the System Profiler if it helps:
MATSHITA DVD-R UJ-845:
+Firmware Revision: DBN9+
+Interconnect: ATAPI+
+Burn Support: Yes (Apple Shipping Drive)+
+Cache: 2048 KB+
+Reads DVD: Yes+
+CD-Write: -R, -RW+
+DVD-Write: -R, -RW, +R, +R DL, RW
+Write Strategies: CD-TAO, CD-SAO, DVD-DAO+
+Media: Insert media and refresh to show available burn speeds+
What can I do to get my CD burner working?

All good suggestions...thanks to all of you weighing in. I have had no issues buring DVDs or CDs (7 months) until this week and am a bit puzzled. Since this verify issue popped up, I've tried buring data from various sources and had some success. As such, I suspect it's not a hardware problem.
I was able to review 1500 JPEGS burned to 1 DVD one-by-one until I found the single file that was an issue. I did this on an XP machine and got a 'cyclic redundancy' error which leads me to believe that I've got a software problem tied to a recent update.
That file is not corrupted at the source and can be copied individually without issue. I've varied burn speeds, media types, file types and data sources and have not been able to identify why 3 of 11 have worked.
The first DVD I burned using dic utility at 4x worked. I felt good that I had a workaround to burning via finder but 3 subsequent attempts with disc utility have failed, too.

SQL version could not be verified error while installing the SCOM 2012 R2 reporting component

I have the below SCOM server roles in my SCOM 2012 R2 set up
1) All servers with Windows Server 2008 R2 SP1, MS - SCOM1, DB & DW - DB1, Reporting Server - DB2
2) All the DB servers with SQL 2012 SP1
3) Windows firewall is turned off on all the servers.
4) Success fully installed all the components except SCOM reporting.
While installing the SCOM 2012 R2 reporting component on DB2 ( Iam running this set up on the server where I instllaed the SQL DB engine and reportin services in Native mode. Configured the SQL reporting database and reporting URLs successfully in SQL reporting
configuration manager) getting the below error in the Rporting server instance page. Kindly advise.
I ran mofcomp.exe and there is no firewall restrictions. My account also has DB owner & sysadmin permissions.
Also tried re installing the SQL on Reporting server.
"The installed version of SQL Server could not be verified or is not supported. Verify that the computer and the installed version of SQL Server meet the minimum requirements for installation, and that the firewall settings are correct. See the Supported
Configurations document for further information".

Hi,
As far as I know, after installing SSRS, we don't need to configure the database and reporting URLs manully. When we install the reporting service for SCOM, it will configure those automatically.
If possible, you may re-install SSRS and then install SCOM reporting service.
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

After getting the dreaded gray/blue screen, I tried to run disk repair on the internal disk. I got an error message saying "Disk Utility can't repair this disk and restore your backed-up files. The volume Macintosh HD could not be verified completely

After getting the dreaded gray/blue screen, I tried to run disk repair on the internal disk. I got an error message saying "Disk Utility can't repair this disk and restore your backed-up files. The volume Macintosh HD could not be verified completely." What do I do now? This is an iMac and I'm running 10.6.8.

Clean Install of Snow Leopard
Be sure to make a backup first because the following procedure will erase
the drive and everything on it. See below for how to clone a drive.
     1. Boot the computer using the Snow Leopard Installer Disc or the Disc 1 that came
         with your computer. Insert the disc into the optical drive and restart the computer.
         After the chime press and hold down the "C" key. Release the key when you see
         a small spinning gear appear below the dark gray Apple logo.
     2. After the installer loads select your language and click on the Continue
         button. When the menu bar appears select Disk Utility from the Utilities menu.
         After DU loads select the hard drive entry from the left side list (mfgr.'s ID and drive
         size.) Click on the Partition tab in the DU main window. Set the number of
         partitions to one (1) from the Partitions drop down menu, click on Options button
         and select GUID, click on OK, then set the format type to MacOS Extended
         (Journaled, if supported), then click on the Apply button.
     3. When the formatting has completed quit DU and return to the installer. Proceed
         with the OS X installation and follow the directions included with the installer.
     4. When the installation has completed your computer will Restart into the Setup
         Assistant. Be sure you configure your initial admin account with the exact same
         username and password that you used on your old drive. After you finish Setup
         Assistant will complete the installation after which you will be running a fresh
         install of OS X. You can now begin the update process by opening Software
         Update and installing all recommended updates to bring your installation current.
Download and install Mac OS X 10.6.8 Update Combo v1.1.
You may be able to backup your data if you have an erased external drive you can use. Before you do the above but after you have opened Disk Utility you can try to clone your drive:
Clone using Restore Option of Disk Utility
1. Open Disk Utility.
2. Select the destination volume from the left side list.
3. Click on the Restore tab in the DU main window.
4. Select the destination volume from the left side list and drag
       it to the Destination entry field.
5. Select the source volume from the left side list and drag it to
      the Source entry field.
6. Double-check you got it right, then click on the Restore button.
Destination means the external backup drive. Source means the internal startup drive.
Now this will only work if the drive is accessible and can be cloned by Disk Utility. Otherwise, you would need to access your drive from another Mac that you can connect via Firewire - Target Disk Mode.

I am using Mac OS X 10.7.5 as of now and when I am trying to upgrade to Mavericks, it is throwing error "The product distribution file could not be verified. It may be damaged or not signed".

I am using Mac OS X 10.7.5 as of now and when I am trying to upgrade to Mavericks, the App Store is throwing error "The product distribution file could not be verified. It may be damaged or not signed".
Is there anything I should do differently? Is anyone else facing the same issue?
Kindly help.

Please read this whole message before doing anything.
This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
Third-party system modifications are a common cause of usability problems. By a “system modification,” I mean software that affects the operation of other software — potentially for the worse. The following procedure will help identify which such modifications you've installed. Don’t be alarmed by the complexity of these instructions — they’re easy to carry out and won’t change anything on your Mac.
These steps are to be taken while booted in “normal” mode, not in safe mode. If you’re now running in safe mode, reboot as usual before continuing.
Below are instructions to enter some UNIX shell commands. The commands are harmless, but they must be entered exactly as given in order to work. If you have doubts about the safety of the procedure suggested here, search this site for other discussions in which it’s been followed without any report of ill effects.
Some of the commands will line-wrap or scroll in your browser, but each one is really just a single line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, and you can then copy it. The headings “Step 1” and so on are not part of the commands.
Note: If you have more than one user account, Step 2 must be taken as an administrator. Ordinarily that would be the user created automatically when you booted the system for the first time. The other steps should be taken as the user who has the problem, if different. Most personal Macs have only one user, and in that case this paragraph doesn’t apply.
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
When you launch Terminal, a text window will open with a line already in it, ending either in a dollar sign (“$”) or a percent sign (“%”). If you get the percent sign, enter “sh” and press return. You should then get a new line ending in a dollar sign.
Step 1
Triple-click anywhere in the line of text below on this page to select it:
kextstat -kl | awk '!/com\.apple/{printf "%s %s\n", $6, $7}' | open -ef
Copy the selected text to the Clipboard by pressing the key combination command-C. Then click anywhere in the Terminal window and paste (command-V). I've tested these instructions only with the Safari web browser. If you use another browser, you may have to press the return key after pasting. A TextEdit window will open with the output of the command. If the command produced no output, the window will be empty. Post the contents of the TextEdit window (not the Terminal window), if any — the text, please, not a screenshot. You can then close the TextEdit window. The title of the window doesn't matter, and you don't need to post that. No typing is involved in this step.
Step 2
Repeat with this line:
{ sudo launchctl list | sed 1d | awk '!/0x|com\.(apple|openssh|vix\.cron)|org\.(amav|apac|cups|isc|ntp|postf|x)/{print $3}'; echo; sudo defaults read com.apple.loginwindow LoginHook; echo; sudo crontab -l; } 2> /dev/null | open -ef
This time you'll be prompted for your login password, which you do have to type. Nothing will be displayed when you type it. Type it carefully and then press return. You may get a one-time warning to be careful. Heed that warning, but don't post it. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
Note: If you don’t have a login password, you’ll need to set one before taking this step. If that’s not possible, skip to the next step.
Step 3
{ launchctl list | sed 1d | awk '!/0x|com\.apple|org\.(x|openbsd)/{print $3}'; echo; crontab -l 2> /dev/null; } | open -ef
Step 4
ls -A /e*/{cr,la,mach}* {,/}Lib*/{Ad,Compon,Ex,Fram,In,Keyb,La,Mail/Bu,P*P,Priv,Qu,Scripti,Servi,Spo,Sta}* L*/Fonts .la* 2> /dev/null | open -ef
Important: If you formerly synchronized with a MobileMe account, your me.com email address may appear in the output of the above command. If so, anonymize it before posting.
Step 5
osascript -e 'tell application "System Events" to get name of login items' | open -ef
Remember, steps 1-5 are all copy-and-paste — no typing, except your password. Also remember to post the output.
You can then quit Terminal.

Application is could not be verified.

Hello Anybody,
I am a new iPhone application developer. I have an application that was working perfectly 'Device 2.2 /Debug' mode. So I want to distribute my application base on 'Ad hoc' method. I was followed all apple instruction. At same time , i have another iPhone application its working perfectly for _device 2.2/debug and Distribution_ mode. I follow the same instruction in this application... When i syn my application to iPhone device 2.2 , i got a error message is *The application "my app name" was not installed on the iPhone "my device name" because it could not be verify.*
Please any help for me..... I spent lot more time taken find out the problem ... I failed.....
Could any one help for me step by step explanation .... How to resolve in this issue
Regards,
NalaN.

I found the solution about the issue .
Solution is : Source code is not sign with machine this is a problem
1)In the File Menu, select New File -> iPhone OS -> Code Signing -> Entitlements.
2) Name the file “Entitlements.plist". and click ‘Finish’. This creates a copy of the default entitlements file within the project.
3) Select the new Entitlments.plist file and uncheck the “get-task-allow” property. Save the Entitlements.plist file
4) Select the Target and open the Build settings inspector. In the ‘Code Signing Entitlements’ build setting, type in the filename of the new Entitlements.plist file including the extension. There is no need to specify a path unless you have put the Entitlements.plist file somewhere other than the top level of the project.

Mavericks Update - Error message - The product distribution file could not be verified

Help!
Trying to download mavericks (from 10.7.5) as I have just had a new hard disk isntalled and need to start from scratch.
Wanting to re download iphoto but I can't as I need a newer OS so trying to download mavericks from the app store. My internet is very slow and keeps cutting out so I have tried a few times but it's not working.
Now I'm getting an error message - 'the product distribution fil could not be verified'
If anyone can help that would be great.
Or even let me know where I can get a copy of iphoto to suit OS 10.7.5 so I don't need to download a whole new OS.

You're trying to download a 5 GB file. If your Internet connection is lousy, you won't have much success. Try another network.

Windows Resource Protection could not perform the requested operation.

A close friend's clear the drive clone the drive using gparted
run chkdsk
fix the master boot run chkdsk again
Now all is well
Upon booting I noticed managed to install at a time, even I ran sfc /scannow backed up the existing CBS log
ran sfc /scannow again
watched the log It started out strong
PS C:\Windows\Logs\CBS> 2014-03-06 18:48:33, Info 002.18005_none_676975d87c 2014-03-06 18:48:33, Info @0xffa949a8 @0xffa930c9 2014-03-06 18:48:33, Info @0x7feff3c3feb 2014-03-06 18:48:33, Info @0xffa94207 @0xffa93125 2014-03-06 18:48:33, Info 2014-03-06 18:48:33, Info sition = @0xb8fad0
2014-03-06 18:48:33, Info 2014-03-06 18:48:33, Info 2014-03-06 18:48:38, Info 2014-03-06 18:48:38, Info 2014-03-06 18:48:39, Info POQ 0 starts:
POQ 0 ends.
2014-03-06 18:48:39, Info 2014-03-06 18:48:39, Info 2014-03-06 18:48:39, Info 2014-03-06 18:48:40, Info POQ 1 starts:
POQ 1 ends.
2014-03-06 18:48:40, Info 2014-03-06 18:48:40, Info 2014-03-06 18:48:40, Info 2014-03-06 18:48:41, Info POQ 2 starts:
POQ 2 ends.
2014-03-06 18:48:41, Info 2014-03-06 18:48:41, Info 2014-03-06 18:48:41, Info 2014-03-06 18:48:41, Info POQ 3 starts:..... and so on
Until it hit a problem
POQ 34 ends.
2014-03-06 18:49:08, Info 2014-03-06 18:49:08, Info 2014-03-06 18:49:08, Info 2014-03-06 18:49:09, Info POQ 35 starts:
POQ 35 ends.
2014-03-06 18:49:09, Info 2014-03-06 18:49:09, Info 2014-03-06 18:49:09, Info 2014-03-06 18:49:10, Info POQ 36 starts:
POQ 36 ends.
2014-03-06 18:49:10, Info 2014-03-06 18:49:11, Info 2014-03-06 18:49:11, Info 2014-03-06 18:49:12, Error ction FileInstaller::CFil [gle=0x80004005]
2014-03-06 18:49:16, Error 2014-03-06 18:49:16, Error 2014-03-06 18:58:33, Info I searched for "[SR]" C:\Windows\system32>findstr 2014-03-06 18:48:38, Info 2014-03-06 18:48:38, Info 2014-03-06 18:48:39, Info 2014-03-06 18:48:39, Info 2014-03-06 18:48:39, Info 2014-03-06 18:48:40, Info 2014-03-06 18:48:40, Info 2014-03-06 18:48:40, Info 2014-03-06 18:48:41, Info 2014-03-06 18:48:41, Info 2014-03-06 18:48:41, Info 2014-03-06 18:48:41, Info 2014-03-06 18:48:42, Info 2014-03-06 18:48:42, Info 2014-03-06 18:48:42, Info 2014-03-06 18:48:42, Info 2014-03-06 18:48:42, Info 2014-03-06 18:48:44, Info 2014-03-06 18:48:44, Info 2014-03-06 18:48:44, Info 2014-03-06 18:48:45, Info 2014-03-06 18:48:45, Info 2014-03-06 18:48:45, Info 2014-03-06 18:48:45, Info 2014-03-06 18:48:46, Info 2014-03-06 18:48:46, Info 2014-03-06 18:48:46, Info 2014-03-06 18:48:47, Info 2014-03-06 18:48:47, Info 2014-03-06 18:48:47, Info 2014-03-06 18:48:48, Info 2014-03-06 18:48:48, Info 2014-03-06 18:48:48, Info 2014-03-06 18:48:48, Info 2014-03-06 18:48:48, Info 2014-03-06 18:48:49, Info 2014-03-06 18:48:49, Info 2014-03-06 18:48:49, Info 2014-03-06 18:48:50, Info 2014-03-06 18:48:50, Info 2014-03-06 18:48:50, Info 2014-03-06 18:48:50, Info 2014-03-06 18:48:51, Info 2014-03-06 18:48:51, Info 2014-03-06 18:48:51, Info 2014-03-06 18:48:51, Info 2014-03-06 18:48:51, Info 2014-03-06 18:48:52, Info 2014-03-06 18:48:52, Info 2014-03-06 18:48:52, Info 2014-03-06 18:48:52, Info 2014-03-06 18:48:53, Info 2014-03-06 18:48:53, Info 2014-03-06 18:48:53, Info 2014-03-06 18:48:54, Info 2014-03-06 18:48:54, Info 2014-03-06 18:48:54, Info 2014-03-06 18:48:54, Info 2014-03-06 18:48:54, Info 2014-03-06 18:48:55, Info 2014-03-06 18:48:55, Info 2014-03-06 18:48:55, Info 2014-03-06 18:48:55, Info 2014-03-06 18:48:56, Info 2014-03-06 18:48:56, Info 2014-03-06 18:48:56, Info 2014-03-06 18:48:56, Info 2014-03-06 18:48:56, Info 2014-03-06 18:48:57, Info 2014-03-06 18:48:57, Info 2014-03-06 18:48:57, Info 2014-03-06 18:48:58, Info 2014-03-06 18:48:58, Info 2014-03-06 18:48:58, Info 2014-03-06 18:49:00, Info 2014-03-06 18:49:00, Info 2014-03-06 18:49:00, Info 2014-03-06 18:49:00, Info 2014-03-06 18:49:01, Info 2014-03-06 18:49:01, Info 2014-03-06 18:49:01, Info 2014-03-06 18:49:02, Info 2014-03-06 18:49:02, Info 2014-03-06 18:49:02, Info 2014-03-06 18:49:02, Info 2014-03-06 18:49:02, Info 2014-03-06 18:49:03, Info 2014-03-06 18:49:03, Info 2014-03-06 18:49:03, Info 2014-03-06 18:49:04, Info 2014-03-06 18:49:04, Info 2014-03-06 18:49:04, Info 2014-03-06 18:49:05, Info 2014-03-06 18:49:05, Info 2014-03-06 18:49:05, Info 2014-03-06 18:49:06, Info 2014-03-06 18:49:06, Info 2014-03-06 18:49:06, Info 2014-03-06 18:49:06, Info 2014-03-06 18:49:07, Info 2014-03-06 18:49:07, Info 2014-03-06 18:49:07, Info 2014-03-06 18:49:08, Info 2014-03-06 18:49:08, Info 2014-03-06 18:49:08, Info 2014-03-06 18:49:08, Info 2014-03-06 18:49:08, Info 2014-03-06 18:49:09, Info 2014-03-06 18:49:09, Info 2014-03-06 18:49:09, Info 2014-03-06 18:49:10, Info 2014-03-06 18:49:11, Info 2014-03-06 18:49:11, Info C:\Windows\system32>
I've run into sfc Is there no way Is that the right Thanks for your time & guidance. machine was blue screening on boot so he had me take a look at it. The error in the BSOD indicated Windows was having trouble reading from the drive. Although the drive wasn't clicking, based on what I was seeing, it seemed pretty
was on its way out. I ran chkdsk, several times, and it found plenty of bad sectors but wasn't able to really fix anything. Fortunately I was able to
record, boot sector and boot configuration data store
the system was dreadfully out of date: Firefox, Java, Reader, Flash - the works - so I updated all that. I also noticed it was missing something like 50-70 Windows updates so I had to straight that right away. It
15-20 before failing with 80070057. This to me isn't too uncommon so I rebooted thinking it wouldn't choke next time. Much to my chagrin, any subsequent attempts fail with error 80070057. I even tried installing just a few updates
just 1, and the error persists. My assumption is that one or more files are maybe damaged and need to be fixed.
and it gets to about 27%, then fails with "Windows Resource Protection could not perform the requested operation." I did the following:
in powershell via Get-Content C:\Windows\Logs\CBS\CBS.log -Wait
Get-Content C:\Windows\Logs\CBS\CBS.log -Wait
CBS Loaded Servicing Stack v6.0.6002.18005 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.0.6
c9b6e6\cbscore.dll
CSI 00000001@2014/3/6:23:48:33.027 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x7fef0cf8c85 @0x7feff3f53ae @0x7feff3c3ed1
@0xffa93578)
CSI 00000002@2014/3/6:23:48:33.045 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x7fef0cf8c85 @0x7feff4386cf @0x7feff4125d9
@0xffa949a8 @0xffa930c9)
CSI 00000003@2014/3/6:23:48:33.048 WcpInitialize (wcp.dll version 0.0.0.5) called (stack @0x7fef0cf8c85 @0x7feff21838d @0x7feff2184ba
@0xffa93578)
CBS NonStart: Checking to ensure startup processing was not required.
CSI 00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDispo
CBS NonStart: Success, startup processing not required as expected.
CSI 00000005 CSI Store 4751600 (0x00000000004880f0) initialized
CSI 00000006 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000007 [SR] Beginning Verify and Repair transaction
CSI 00000008 Repair results created:
CSI 00000009 [SR] Verify complete
CSI 0000000a [SR] Verifying 100 (0x0000000000000064) components
CSI 0000000b [SR] Beginning Verify and Repair transaction
CSI 0000000c Repair results created:
CSI 0000000d [SR] Verify complete
CSI 0000000e [SR] Verifying 100 (0x0000000000000064) components
CSI 0000000f [SR] Beginning Verify and Repair transaction
CSI 00000010 Repair results created:
CSI 00000011 [SR] Verify complete
CSI 00000012 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000013 [SR] Beginning Verify and Repair transaction
CSI 00000014 Repair results created:
CSI 00000091 [SR] Verify complete
CSI 00000092 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000093 [SR] Beginning Verify and Repair transaction
CSI 00000094 Repair results created:
CSI 00000095 [SR] Verify complete
CSI 00000096 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000097 [SR] Beginning Verify and Repair transaction
CSI 00000098 Repair results created:
CSI 00000099 [SR] Verify complete
CSI 0000009a [SR] Verifying 100 (0x0000000000000064) components
CSI 0000009b [SR] Beginning Verify and Repair transaction
CSI 0000009c@2014/3/6:23:49:12.802 (F) d:\longhorn\base\wcp\primitiveinstallers\filehierarchy.cpp(1939): Error STATUS_INVALID_PARAMETER originated in fun
eInstallerHierarchy::PortFileInformationBetweenCdfs expression: TmpBlob.Length == sizeof(LUACDF_FILE_ENTRY)
CSI 0000009d (F) STATUS_INVALID_PARAMETER #2119209# from CFileInstaller::CommitChanges(...)[gle=0xd000000d]
CSI 0000009e (F) STATUS_INVALID_PARAMETER #2119208# from PrimitiveInstaller::CCoordinator::FinalizeChanges(...)[gle=0xd000000d]
CBS Scavenge: Package store indicates there is no component to scavenge, skipping.
but I didn't see anything of great interest
/c:"[SR]" %windir%\logs\cbs\cbs.log
CSI 00000006 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000007 [SR] Beginning Verify and Repair transaction
CSI 00000009 [SR] Verify complete
CSI 0000000a [SR] Verifying 100 (0x0000000000000064) components
CSI 0000000b [SR] Beginning Verify and Repair transaction
CSI 0000000d [SR] Verify complete
CSI 0000000e [SR] Verifying 100 (0x0000000000000064) components
CSI 0000000f [SR] Beginning Verify and Repair transaction
CSI 00000011 [SR] Verify complete
CSI 00000012 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000013 [SR] Beginning Verify and Repair transaction
CSI 00000015 [SR] Verify complete
CSI 00000016 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000017 [SR] Beginning Verify and Repair transaction
CSI 00000019 [SR] Verify complete
CSI 0000001a [SR] Verifying 100 (0x0000000000000064) components
CSI 0000001b [SR] Beginning Verify and Repair transaction
CSI 0000001d [SR] Verify complete
CSI 0000001e [SR] Verifying 100 (0x0000000000000064) components
CSI 0000001f [SR] Beginning Verify and Repair transaction
CSI 00000021 [SR] Verify complete
CSI 00000022 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000023 [SR] Beginning Verify and Repair transaction
CSI 00000025 [SR] Verify complete
CSI 00000026 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000027 [SR] Beginning Verify and Repair transaction
CSI 00000029 [SR] Verify complete
CSI 0000002a [SR] Verifying 100 (0x0000000000000064) components
CSI 0000002b [SR] Beginning Verify and Repair transaction
CSI 0000002d [SR] Verify complete
CSI 0000002e [SR] Verifying 100 (0x0000000000000064) components
CSI 0000002f [SR] Beginning Verify and Repair transaction
CSI 00000031 [SR] Verify complete
CSI 00000032 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000033 [SR] Beginning Verify and Repair transaction
CSI 00000035 [SR] Verify complete
CSI 00000036 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000037 [SR] Beginning Verify and Repair transaction
CSI 00000039 [SR] Verify complete
CSI 0000003a [SR] Verifying 100 (0x0000000000000064) components
CSI 0000003b [SR] Beginning Verify and Repair transaction
CSI 0000003d [SR] Verify complete
CSI 0000003e [SR] Verifying 100 (0x0000000000000064) components
CSI 0000003f [SR] Beginning Verify and Repair transaction
CSI 00000041 [SR] Verify complete
CSI 00000042 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000043 [SR] Beginning Verify and Repair transaction
CSI 00000045 [SR] Verify complete
CSI 00000046 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000047 [SR] Beginning Verify and Repair transaction
CSI 00000049 [SR] Verify complete
CSI 0000004a [SR] Verifying 100 (0x0000000000000064) components
CSI 0000004b [SR] Beginning Verify and Repair transaction
CSI 0000004d [SR] Verify complete
CSI 0000004e [SR] Verifying 100 (0x0000000000000064) components
CSI 0000004f [SR] Beginning Verify and Repair transaction
CSI 00000051 [SR] Verify complete
CSI 00000052 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000053 [SR] Beginning Verify and Repair transaction
CSI 00000055 [SR] Verify complete
CSI 00000056 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000057 [SR] Beginning Verify and Repair transaction
CSI 00000059 [SR] Verify complete
CSI 0000005a [SR] Verifying 100 (0x0000000000000064) components
CSI 0000005b [SR] Beginning Verify and Repair transaction
CSI 0000005d [SR] Verify complete
CSI 0000005e [SR] Verifying 100 (0x0000000000000064) components
CSI 0000005f [SR] Beginning Verify and Repair transaction
CSI 00000061 [SR] Verify complete
CSI 00000062 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000063 [SR] Beginning Verify and Repair transaction
CSI 00000065 [SR] Verify complete
CSI 00000066 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000067 [SR] Beginning Verify and Repair transaction
CSI 00000069 [SR] Verify complete
CSI 0000006a [SR] Verifying 100 (0x0000000000000064) components
CSI 0000006b [SR] Beginning Verify and Repair transaction
CSI 0000006d [SR] Verify complete
CSI 0000006e [SR] Verifying 100 (0x0000000000000064) components
CSI 0000006f [SR] Beginning Verify and Repair transaction
CSI 00000071 [SR] Verify complete
CSI 00000072 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000073 [SR] Beginning Verify and Repair transaction
CSI 00000075 [SR] Verify complete
CSI 00000076 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000077 [SR] Beginning Verify and Repair transaction
CSI 00000079 [SR] Verify complete
CSI 0000007a [SR] Verifying 100 (0x0000000000000064) components
CSI 0000007b [SR] Beginning Verify and Repair transaction
CSI 0000007d [SR] Verify complete
CSI 0000007e [SR] Verifying 100 (0x0000000000000064) components
CSI 0000007f [SR] Beginning Verify and Repair transaction
CSI 00000081 [SR] Verify complete
CSI 00000082 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000083 [SR] Beginning Verify and Repair transaction
CSI 00000085 [SR] Verify complete
CSI 00000086 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000087 [SR] Beginning Verify and Repair transaction
CSI 00000089 [SR] Verify complete
CSI 0000008a [SR] Verifying 100 (0x0000000000000064) components
CSI 0000008b [SR] Beginning Verify and Repair transaction
CSI 0000008d [SR] Verify complete
CSI 0000008e [SR] Verifying 100 (0x0000000000000064) components
CSI 0000008f [SR] Beginning Verify and Repair transaction
CSI 00000091 [SR] Verify complete
CSI 00000092 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000093 [SR] Beginning Verify and Repair transaction
CSI 00000095 [SR] Verify complete
CSI 00000096 [SR] Verifying 100 (0x0000000000000064) components
CSI 00000097 [SR] Beginning Verify and Repair transaction
CSI 00000099 [SR] Verify complete
CSI 0000009a [SR] Verifying 100 (0x0000000000000064) components
CSI 0000009b [SR] Beginning Verify and Repair transaction
issues in the past, and in one instance, booting the OS install DVD, and running sfc /scannow /offbootdir=c:\ /offwindir=c:\windows did fix the issue. But I have to ask
to do that while in Windows? Can't I mount some WIM and do it that way instead of booting the DVD?
course of action, or is/are there some other options I should explore?

Hi,
In my opinion, if you want SFC to use a sourcepath to repair your system, you can just use in-place upgrade to do this:
How to Perform an In-Place Upgrade on Windows Vista, Windows 7, Windows Server 2008 & Windows Server 2008 R2
http://support.microsoft.com/kb/2255099
If you have any feedback on our support, please click
here
Alex Zhao
TechNet Community Support
Thanks for taking the time to reply and for this suggestion.
The in-place upgrade is a wonderful potential solution, but the process requires the source media. Most systems these days don't include the OS or recovery CD's because the manufacturers want you to pay for them. And most consumers aren't spending
the $50-$70 dollars to get the media, which complicates things in situations like this. So while they've purchased a machine and have a valid Microsoft COA sticker on the box, they can't do anything.
Also, to make matters worse, I posted this in the wrong forum as this is a Vista Home Premium PC. [My sincere apologies for that. Mods please feel free to move/reclassify] I do have a Vista Home Premium DVD, but its the 32-bit version, not 64-bit,
which is what this system is. So unless I can locate a Visa Home Premium 64-bit DVD, or they upgrade to Windows 7 or 8 (which they probably should do anyway), we're sunk.

"image size could not be verified - operation not performed" when I go to restore to my hard drive. What do?

I want to restore my disk image using disk utility. I keep getting "image size could not be verified - operation not performed" when I go to restore to my hard drive. What do?
I would like to partition my disk but it says I have to restore my disk image first so that files can be moved. This is really obnoxiously hard for someone who is only moderately tech savy. Any help is appreciated, but please no links to 3rd party sites. I would like to keep this with the software I already have.
Thanks ^_^

Sorry nobody has replied yet, but how was this disk image made?
"Try Disk Utility
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Select your Mac OS X volume.
5. Click Repair Disk, (not Repair Permissions). Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)
If perchance you can't find your install Disc, at least try it from the Safe Boot part onward.

Configuration could not be verified - is the username or password wrong?

I run Windows 7 Professional 32 bit. Downloaded and installed Tbird 31.1.1 today.
Logged in to my Gmail account using copy and paste of my username and password from a file. I enabled IMAP. Logged out of my Gmail account.
Turned off Windows Firewall. My task bar is red at me with 1 important message: Windows Security Center Service (Important) The Windows Security Center service is turned off.
I have no antivirus software installed other than Microsoft Security Essentials (MSE.) I went to Control Panel | Programs and looked, finding nothing. This was to be expected because I haven't installed antivirus software before.
Restarted in Safe Mode with networking, which seems to turn off MSE.
Back in TB, I clicked Create a new account: Email. Entered my name, Google E-mail address, Google password. I used copy and paste to enter the same Gmail address and password that worked for my login minutes previously. It autopopulated the fields. I clicked Done. After a few seconds, got the error message:
Configuration could not be verified - is the username or password wrong?
So with no antivirus software, no firewall, and restarted in safe mode, what is the problem?
Thanks.

I tried again today without success. I have been able to get Tbird to download mail from a non-Gmail provider but not send messages with this non-Gmail account.
I have enabled 2-factor authentication in Gmail for this account. I followed the instructions from Toad Hall at 9/20/14 1:28 PM here https://support.mozilla.org/en-US/questions/1020778
I got the password from Google and went to Tbird. I went to Tools | Options | Security | Passwords and deleted all the Gmail entries. I shut down and restarted Tbird. I highlighted the Gmail account I created and hit F5. Nothing at all happened. I deleted the account and tried to recreate the account again. I got the familiar error message that Tbird cannot set up the Gmail account. So now what?

PGP signatures could not be verified

I'm still somewhat new on using makepkg. I previously customized the bind pkg for samba by copying the /var/abs/extra/bind directory into my /var/abs/local and adding a couple of build options. Worked like a charm and no issues.
Today bind 9.10.2 was released and I wanted to update my package but I get:
ERROR: One or more PGP signatures could not be verified! when updating using the latest abs bind package.
==> Making package: bind 9.10.2-1 (Wed Mar 4 16:47:20 PST 2015)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading bind-9.10.2.tar.gz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 8282k 100 8282k 0 0 5669k 0 0:00:01 0:00:01 --:--:-- 5672k
-> Downloading bind-9.10.2.tar.gz.asc...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 490 100 490 0 0 6640 0 --:--:-- --:--:-- --:--:-- 6712
-> Found tmpfiles.conf
-> Found sysusers.conf
-> Found named.conf
-> Found named.service
-> Found localhost.zone
-> Found localhost.ip6.zone
-> Found 127.0.0.zone
-> Found empty.zone
==> Validating source files with sha1sums...
bind-9.10.2.tar.gz ... Passed
bind-9.10.2.tar.gz.asc ... Skipped
tmpfiles.conf ... Passed
sysusers.conf ... Passed
named.conf ... Passed
named.service ... Passed
localhost.zone ... Passed
localhost.ip6.zone ... Passed
127.0.0.zone ... Passed
empty.zone ... Passed
==> Verifying source file signatures with gpg...
bind-9.10.2.tar.gz ... FAILED
==> ERROR: One or more PGP signatures could not be verified!
this is the abs bind package....why is it failing?

Same error here.
==> Validando arquivos fonte com sha256sums...
firefox-36.0.1.source.tar.bz2 ... Passou
firefox-36.0.1.source.tar.bz2.asc ... Ignorada
mozconfig ... Passou
firefox.desktop ... Passou
firefox-install-dir.patch ... Passou
vendor.js ... Passou
rhbz-966424.patch ... Passou
firefox-fixed-loading-icon.png ... Passou
==> Verificando assinatura de arquivo fonte com gpg...
firefox-36.0.1.source.tar.bz2 ... FALHOU (chave pública desconhecida 057CC3EB15A0A4BC)
==> ERRO: Uma ou mais assinaturas PGP não puderam ser verificadas!
I have checked (http://allanmcrae.com/2015/01/two-pgp-k … rch-linux/) but to no avail.
I do not understand why complicate things when they are working perfectly how it worked before...

Macintosh HD could not be verified completely

Own a Mac air (purchased late 2012) haven't had issues until today when it would not start up. It chimed, the grey apple appeared. Then nothing. Ran a verify disk and got a message the Hd could not be verified and error: this disk needs to be repaired. I clicked the Repair Disk which then says disk utility can't repair this disk.
So to complicate this issue a backup has not been done recently and we live out of country and don't have access to an Apple store. We have an iPad, which I am using now and have an external disk drive but that's all we have to work with. :(
Is there a way to back up the data from a safe mode or whatever Mac calls it? And could a problem with a file system cause the error? If so, how can that be fixed. Any help is appreciated.
Thanks

So it will boot the Recovery Partition quickly and you show you options for Disk Utility and Reinstall OS X (among others). That is a good sign.
Try booting in Safe Mode and then running a Time Machine (or other) backup.
(You cannot backup to a Time Capsule while in Safe Boot mode.)
Press the power button and as you hear the bong hold down the Shift key.
If it will boot then run a Time Machine backup.
Time Machine Basics: http://support.apple.com/kb/ht1427
If you could not compete a backup from Safe Mode then skip to the Emergency Data Recovery below before attempting to repair the disk.
Repairing the Disk and Reinstalling OS X.
Boot the Recovery Partition and start Disk Utility.
Click on your system volume (Macintosh HD).
If the S.M.A.R.T status does not say “Verified” then when you are done with these procedures the SSD will need to be replaced.
Repair Disk.
If it did not repair completely the first time, try once more.
Try a Safe Mode boot to backup the data and then a normal boot.
If a normal boot did not work boot the Recovery Partition and reinstall OS X.
Try a Safe Mode boot to backup the data and then a normal boot.
If a normal boot did not work it is time for a clean install. This will wipe all data from the SSD. Hopefully by now you have recovered your data.
Unplug any external disks.
Boot the Recovery Partition.
Format the system drive using the procedures below, selecting the system disk.
Reinstall OS X.
Boot normally. If it still won’t boot then there is something still wrong with the SSD or other hardware.
If it boots normally, this time it will ask to reload the data.
Tell it to reload your data from your Time Machine backup or the emergency data recovery disk.
Recover data by booting from an external system disk:
You will need an external drive which you will erase for this procedure.
(Do not erase your existing backup, even if it is not current.)
Format the external disk as instructed below.
Install OS X onto that external disk, booting the Recovery Partition.
Boot from that external disk (Boot then hold down Option).
Using the Finder drag as many folders as you can to the external disk.
Formatting the external drive:
Boot the recovery partition.
Format (and erase) the destination recovery disk:
          Plug in the drive you are about to erase.
          Select the volume that is NOT your system disk.
          Click on Partition.
          Pull down under Partition Layout to 1 Partition.
          Click on Options…
          Select GUID Partition Table.
          Name: Emergency Backup
          Format: Select Mac OS Extended (journaled)
          Click Apply.
          Click Partition.
Once your system is healthy again be sure to maintain one or two reasonably current backups.
More about backups:
Time Machine Basics: http://support.apple.com/kb/ht1427
Most commonly used backup methods: https://discussions.apple.com/docs/DOC-3045
Methodology to protect your data. Backups vs. Archives. Long-term data protection: https://discussions.apple.com/docs/DOC-6031

I tried to update, but my apple ID does not allowing me , always giving me 'Your device or computer could not be verified. Contact support for assistance

I tried to update, but my apple ID does not allowing me , always giving me 'Your device or computer could not be verified. Contact support for assistance '. I changed my apple ID passwords, still same. help me please

Back up all data before proceeding.
Step 1
Triple-click anywhere in the line below on this page to select it:
/Library/Preferences/SystemConfiguration/NetworkInterfaces.plist
Right-click or control-click the line and select
Services ▹ Reveal in Finder (or just Reveal)
from the contextual menu.* A folder should open with an item selected. Move the selected item to the Trash. You may be prompted for your administrator login password. Restart the computer and test.
*If you don't see the contextual menu item, copy the selected text to the Clipboard by pressing the key combination command-C. In the Finder, select
Go ▹ Go to Folder...
from the menu bar and paste into the box that opens by pressing command-V. You won't see what you pasted because a line break is included. Press return.
Log out, log back in, and test. If there's no improvement, continue.
Step 2
Reset your computer’s PRAM.

HT5625 My daughter and I were both on same Apple ID. We are trying to change hers but when we do, it says her email is already associated with an Apple ID but when we try to get the password, it says that it could not be verified. How do we correct this?

My daughter and I were both on same Apple ID. We are trying to change hers but when we do, it says her email is already associated with an Apple ID but when we try to get the password, it says that it could not be verified. How do we correct this?

Not from your end. Click here and ask the iTunes Store staff for assistance.
(126716)

"Disc copy protection could not be verified."

Similar Messages

Maybe you are looking for