T530 invalid uuid

Similar Questions

• BlackBerry Obex - UUID problem invalid?

  Hello.

  I get this invalid "UUID" error when you try to start my bluetooth server.

  Don't know what the problem is. Pointers?

  need more information, just ask me.

  Thank you

  Okay, whatever my problem... Well my problem actually really simple and stupid. What I got wrong was to have a space between the "localhost:"and the uuid, I join it. "

  So that was my problem...

• [S531] UUID is invalid, how Flash BIOS?

  Hello!

  My Lenovo Thinkpad S531 gives me an error message whenever I restart the computer that the UUID is invalid. This does not affect the performance but is really boring because of the beeps sounds.

  I discovered that this error can be resolved using the WinPhlash.exe to backup the BIOS. Unfortunately, the program shows me the error code - 100: BCPSYS block signature not found.

  What can I do to avoid this error message, or how do I enter the UUID of the motherboard BIOS. I do not have a guarantee of more and each piece is an original part of Lenovo.
  I use Windows 7 64-bit.

  Please help me, because I feel that I searched through the whole internet and I found quite well how to get rid of this annoying error, but another error prevents me to do.

  Thank you and have a nice day!

  Only dealers and service providers have the disc.

• Motherboard model H535 failure - the type of machine and the serial number invalid after replacement

  Does anyone know how to set the new Type of Machine and the serial number after a motherboard for a replacement model H535?

  The motherboard has recently failed on my model H535 (7 months after the expiration of the warranty - thanks, Lenovo). No local garage would agree to replace due to its nature of owners (thanks, Lenovo). I spent about four hours on the phone being bounced into back-and-forth between the many support staff (usually combined) Lenovo in sales, technical support, support of parts of IBM and various other departments (thanks, Lenovo), which one has suggested that I might have to try to find a motherboard on Ebay or Amazon for my computer in less-than-2-year-old. However, I finally get to someone at Lenovo, which has been able to sell a motherboard - for 2/3 of the cost of the original computer.

  Now, I installed the motherboard, and it works. However, during each boot, I get a POST with two beeps error which reads as follows:

  00CE error: Machine Type and serial number is INVALID

  Start of manufacturing sequence is taken if no selection is made

  I presume that the BIOS on the new motherboard must be programmed with the right Type of Machine and the serial number of my computer. I've read various things on the Internet about what to do, as updating the BIOS (I can not even find a BIOS under "downloads" of support for the H535 - thanks, Lenovo model), using WinPhlash (I apparently need one kind of BIOS ROM file to make it work, I don't have), getting a Lenovo hardware maintenance disk for my model (which apparently isn't available for other special people only me - thanks Lenovo), etc.

  The waiting time for Lenovo support are ridiculously long, and almost every customer support person is ridiculously uninformed on the difference between one of their computer models, and even less their motherboards (thanks, Lenovo). I am amazed and extremely frustrated. It shouldn't be rocket science.

  On a side note, I initially bought the computer from Staples with a credit card with extended warranty protection, which means I can get a refund for repair. Although the motherboard came with a packing list, no Bill has been provided by Lenovo, and I couldn't make them send one - or maybe even with success to explain what a Bill is (thanks, Lenovo).

  Well, Lenovo support was useless, and any alleged authorized suppliers were in fact still suppliers or could help with my problem. But I was finally able to fix it myself. Once I found the right piece of software, it has been fixed in less than a minute.

  My BIOS is by American Megatrends, and I discovered that they have a set of utilities that includes a called AMIDEDOS. It is intended for manufacturers to be able to change the strings of text stored in the BIOS for things like the manufacturer, product name, Version, number series, UUID, SKU number, family, etc., that is what I had to do. It is not intended for use by consumers, but it's there.

  When I ran the "DMIEdit.exe" program AMIDEDOS (clicked and ran as administrator from 10 Windows) and click on "System information" from the list, I saw "Product Name | STRING | Invalid' and ' serial number | STRING | NOT VALID ". The other fields appeared to have valid entries. I double-clicked on the fields valid and changed their "H535 model" and the serial number of my computer, respectively and then clicked on "Update all" at the top.

  Much to my surprise, he reported that he had successfully registered the new information. And, perhaps even more surprising is the fact that, when I rebooted, the double beep and the warning about the type of computer not valid and serial number have disappeared. In addition, the BIOS showed I had entered the new values, and the 'Manufacturing Boot Sequence' option (I understand can be much slower than a normal boot) had disappeared.

  Again, I'm a little surprised simple it was actually solve the problem once I got the correct software, or Lenovo part nor American Megatrends apparently offers to the owners, and it took hours and hours of research and research to understand. Use this information at your own risk, however, as playing with BIOS apparently can lead to problems not easily solved. That said, the modification of these text strings seems relatively safe.

  I will mention that I also ended up changing the method of "LEGACY" to "UEFI" boot in the BIOS after noticing that the selection.

• T530 serial # location?

  Certified refurbished standard T530:

  The manual says the nunmber series is the #. I don't see a ME # on the outer surface or inside the battery bay. The manual says it is on the bottom of the machine, but only the current issue begins: NLENT...?

  Mark

  Hello, markg2

  As the camera is refurbished, its s/n on the case may not match the internal data.

  So you might check:
  -Press win + R, type cmd
  copy-past the next string in the open window, by right-clicking
  WMIC.exe csproduct get vendor, name, identifyingnumber, uuid

  "identifyingnumber" means computer laptop s/n

• Error UUID trying to convert VMS

  I'm trying to convert a virtual machine by vCenter Converter Standalone v5.5 (5.5.0 build-1362012). When I select the virtual machine and press Next, the following error message is displayed: "a general error has occurred: Invalid Argument".

  The log file shows the following error: "ManagedVmLocation has no MoRef VM or VM UUID.

  How can I solve this?

  Thank you.

  It would be a valid uuid. For example, copy it to leave uuid.bios and change a few numbers in there.

  Concerning

• [SOLVED] Help fixing 'file two systems with the same uuid were detected.

  I have a Setup ESXi embedded (installed on a USB key connected to the internal USB port) on a Dell T710 with few of the SAS drives.  I tried the upgrade to 4.0 - 294855 to 4.1 - 348481 by following the instructions here via:

  esxupdate--bundle=/vmfs/volumes/datastore_name/path/to/upgrade-from-esxi4.0-to-4.1-update01-348481.zip update

  Even if it is done correctly, when I restarted I got a purple screen with this message on this subject:

  The system has found a problem on your machine and cannot continue.

  Two systems with the same UUID files have been detected.  Make sure that you do not have two installations of ESXi.

  So, he tried to update one of the SAS drives internal versus inside USB key...?

  I studied this time before & found a threadwhere posted to help, but it wasn't enough to get me going.  Tonight, I found KB1035107 which details how to fix this, but I have a few concerns:

  • How can I identify the drive that has the invalid ESXi installation?
    
  • Better yet: How can I identify who / disc is the one with the ESXi installation I want to keep?
    
    • I know that I can use esxcfg-mpath-l., esxcfg-mpath-band esxcfg-scsidevs-l to collect the disk & LUN information.  But what happens if it wasn't a built-in installation?  If ESXi was installed on one of the SAS drives, how could I confirm which drive it actually installed on?
      
  • What is the worst that could happen with the performance he commands in the KB above?
    
    • Do I need to worry about migration whatever data is stored elsewhere there until I can get through this?
      

  Finally, and perhaps more important than these other issues:

  It is for me a way to specify which disk/drive/device to target when executing upgrades, more precisely from 4.0 to 4.1?

  How can I perform upgrades in the future without having to worry about this nonsense?  I don't want to have to disconnect from the LUN/warehouses of data whenever there is an upgrade (major or minor).

  
  Thank you very much.

  Did the HD with the data store show other partitions if your running fdisk-l?

• Crash when the instant withdrawal: State of the virtual machine is 'unknown (invalid) '.

  Hi all

  Currently, I'm in the middle of a nightmare: a few moments I tried to delete a snapshot that has been there for a while on one of my virtual machines. Of course, it can take a loy of time for this kind of operation to achieve, so I waited patiently so that it reaches its end.

  But in the middle of it my host had a kernel panic (I'll have to diagnose this one).

  When I got to new host, the virtual machine was not the webui, try saving it shows the machine as being "unknow (invalid)"...

  I scoured Suur intrenet for a while, but everything I have read until knowledge is quiet frightneging.

  Currently, the directory that stores all the files of the virtual machine is looking as follows:

  drwxrwxrwx 2 root root 4096 12 October 2008 564d583c-363e-0c7a-96e0-cd07d5b1a8e1.vmem.lck

  -rw - 1 root root 2147221504 2 May 20:31 colossus2_2new - f001.vmdk

  -rw - 1 root root 2147221504 19 Dec 13:04 colossus2_2new - f002.vmdk

  -rw - 1 root root 1074266112 Jan 11 22:27 colossus2_2new - f003.vmdk

  -rw - 1 root root 528 2 May 20:31 colossus2_2new.vmdk

  -rw - 1 root root 2147221504 2 May 20:32 colossus2_3new - f001.vmdk

  -rw - 1 root root 2147221504 2 May 20:32 colossus2_3new - f002.vmdk

  -rw - 1 root root 2147221504 2 May 20:32 colossus2_3new - f003.vmdk

  -rw - 1 root root 2147221504 19 Dec 13:04 colossus2_3new - f004.vmdk

  -rw - 1 root root 2147221504 Jan 11 22:35 colossus2_3new - f005.vmdk

  -rw - 1 root root 1310720 Jan 11 22:35 colossus2_3new - f006.vmdk

  -rw - 1 root root 661 2 May 20:32 colossus2_3new.vmdk

  -rw - 1 root root 2147221504 2 May 20:32 colossus2_4new - f001.vmdk

  -rw - 1 root root 2147221504 2 May 20:33 colossus2_4new - f002.vmdk

  -rw - 1 root root 2147221504 2 May 20:33 colossus2_4new - f003.vmdk

  -rw - 1 root root 2147221504 2 May 20:34 colossus2_4new - f004.vmdk

  -rw - 1 root root 2147221504 2 May 20:35 colossus2_4new - f005.vmdk

  -rw - 1 root root 1310720 Jan 11 22:42 colossus2_4new - f006.vmdk

  -rw - 1 root root 661 2 May 20:35 colossus2_4new.vmdk

  -rw - 1 root root 1868365824 2 May 22:13 colossus2_5new-000001 - s001.vmdk

  -rw - 1 root root 1637482496 2 May 22:13 colossus2_5new-000001 - s002.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s003.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s004.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s005.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s006.vmdk

  -rw - 1 root root 2096824320 2 May 22:13 colossus2_5new-000001 - s007.vmdk

  -rw - 1 root root 554369024 2 May 22:13 colossus2_5new-000001 - s008.vmdk

  -rw - 1 root root 1728839680 2 May 22:13 colossus2_5new-000001 - s009.vmdk

  -rw - 1 root root 2114191360 2 May 22:13 colossus2_5new-000001 - s010.vmdk

  -rw - 1 root root 1659371520 2 May 22:13 colossus2_5new-000001 - s011.vmdk

  -rw - 1 root root 1527775232 2 May 22:13 colossus2_5new-000001 - s012.vmdk

  -rw - 1 root root 1578958848 2 May 22:13 colossus2_5new-000001 - s013.vmdk

  -rw - 1 root root 1611792384 2 May 22:13 colossus2_5new-000001 - s014.vmdk

  -rw - 1 root root 1602945024 2 May 22:13 colossus2_5new-000001 - s015.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s016.vmdk

  -rw - 1 root root 2085617664 2 May 22:13 colossus2_5new-000001 - s017.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s018.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s019.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s020.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s021.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s022.vmdk

  -rw - 1 root root 2114256896 2 May 22:13 colossus2_5new-000001 - s023.vmdk

  -rw - 1 root root 132055040 2 May 22:13 colossus2_5new-000001 - s024.vmdk

  -rw - 1 root root 327680 2 May 22:13 colossus2_5new-000001 - s025.vmdk

  -rw - 1 root root 65536 2 May 22:13 colossus2_5new-000001 - s026.vmdk

  -rw - 1 root root 1582 Mar 8 17:53 colossus2_5new - 000001.vmdk

  drwxrwxrwx 3 root root 4096 2 May 22:14 colossus2_5new - 000001.vmdk.lck

  -rw - 1 root root 2147221504 2 May 20:36 colossus2_5new - f001.vmdk

  -rw - 1 root root 2147221504 2 May 20:36 colossus2_5new - f002.vmdk

  -rw - 1 root root 2147221504 2 May 20:37 colossus2_5new - f003.vmdk

  -rw - 1 root root 2147221504 2 May 20:38 colossus2_5new - f004.vmdk

  -rw - 1 root root 2147221504 2 May 20:39 colossus2_5new - f005.vmdk

  -rw - 1 root root 2147221504 2 May 20:41 colossus2_5new - f006.vmdk

  -rw - 1 root root 2147221504 2 May 20:42 colossus2_5new - f007.vmdk

  -rw - 1 root root 2147221504 2 May 20:42 colossus2_5new - f008.vmdk

  -rw - 1 root root 2147221504 2 May 20:43 colossus2_5new - f009.vmdk

  -rw - 1 root root 2147221504 2 May 20:45 colossus2_5new - f010.vmdk

  -rw - 1 root root 2147221504 2 May 20:46 colossus2_5new - f011.vmdk

  -rw - 1 root root 2147221504 2 May 20:46 colossus2_5new - f012.vmdk

  -rw - 1 root root 2147221504 2 May 20:47 colossus2_5new - f013.vmdk

  -rw - 1 root root 2147221504 2 May 20:47 colossus2_5new - f014.vmdk

  -rw - 1 root root 2147221504 2 May 20:48 colossus2_5new - f015.vmdk

  -rw - 1 root root 2147221504 Feb 11 13:19 colossus2_5new - f016.vmdk

  -rw - 1 root root 2147221504 8 Mar 17:17 colossus2_5new - f017.vmdk

  -rw - 1 root root 2147221504 Jan 11 23:02 colossus2_5new - f018.vmdk

  -rw - 1 root root 2147221504 Jan 11 23:03 colossus2_5new - f019.vmdk

  -rw - 1 root root 2147221504 Jan 11 23:03 colossus2_5new - f020.vmdk

  -rw - 1 root root 2147221504 Jan 11 23:03 colossus2_5new - f021.vmdk

  -rw - 1 root root 2147221504 19 Dec 13:04 colossus2_5new - f022.vmdk

  -rw - 1 root root 2147221504 Jan 11 23:04 colossus2_5new - f023.vmdk

  -rw - 1 root root 2147221504 Jan 11 23:05 colossus2_5new - f024.vmdk

  -rw - 1 root root 2147221504 Jan 11 23:05 colossus2_5new - f025.vmdk

  -rw - 1 root root by 6553600 Jan 11 23:05 colossus2_5new - f026.vmdk

  -rw - 1 root root 1562 2 May 20:35 colossus2_5new.vmdk

  -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f001.vmdk

  -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f002.vmdk

  -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f003.vmdk

  -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f004.vmdk

  -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f005.vmdk

  -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f006.vmdk

  -rw - 1 root root 2147221504 2 May 20:31 colossus2 - f007.vmdk

  -rw - 1 root root 1075576832 2 May 20:31 colossus2 - f008.vmdk

  -rw - 1 root root 8684 2 May 20:19 colossus2.nvram

  -rw - 1 root root 714 2 May 20:31 colossus2.vmdk

  -rw - 1 root root 821 2 May 20:31 colossus2.vmsd

  drwxrwxrwx 2 root root 4096 2 May 22:13 colossus2.vmsd.lck

  -rwxr-xr-x 1 root root 2680 may 2 21:35 colossus2.vmx

  -rw - 1 root root 264 Jan 11 22:25 colossus2.vmxf

  -rw - rr 1 root root 98347008 1 October 2008 gparted-live - 0.3.9 - 4.ISO

  -rw - rr 1 root root 1581428 Jan 13 11:53 0.log - vmware

  -rw - rr 1 root root 771239 19 Dec 12:59 vmware - 1.log

  -rw - rr 1 root root 76388 Jan 11 23:21 vmware - 2.log

  -rw - rr 1 root root 10161063 2 May 20:18 vmware.log

  The vmx file contains the following:

  #! / usr/bin/vmware

  . Encoding = 'UTF-8 '.

  config.version = '8 '.

  virtualHW.version = "7".

  floppy0. Present = "FALSE".

  MKS. Enable3D = 'TRUE '.

  pciBridge0.present = 'TRUE '.

  pciBridge4.present = 'TRUE '.

  pciBridge4.virtualDev = "pcieRootPort"

  pciBridge4.functions = '8 '.

  pciBridge5.present = 'TRUE '.

  pciBridge5.virtualDev = "pcieRootPort"

  pciBridge5.functions = '8 '.

  pciBridge6.present = 'TRUE '.

  pciBridge6.virtualDev = "pcieRootPort"

  pciBridge6.functions = '8 '.

  pciBridge7.present = 'TRUE '.

  pciBridge7.virtualDev = "pcieRootPort"

  pciBridge7.functions = '8 '.

  vmci0. Present = 'TRUE '.

  NVRAM = "colossus2.nvram."

  virtualHW.productCompatibility = "hosted".

  FT.secondary0.enabled = 'TRUE '.

  Tools.Upgrade.Policy = "useGlobal".

  powerType.powerOff = 'soft '.

  powerType.powerOn = "hard."

  powerType.suspend = "hard."

  powerType.reset = 'soft '.

  displayName = "colossus2."

  extendedConfigFile = "colossus2.vmxf".

  scsi0. Present = 'TRUE '.

  scsi0.sharedBus = 'none '.

  scsi0.virtualDev = "free".

  memsize = "4096".

  scsi0:0. Present = 'TRUE '.

  scsi0:0. FileName = "colossus2.vmdk".

  IDE1:0. Present = "FALSE".

  IDE1:0. FileName = ' / vmachines/colossus2/gparted-live-0.3.9-4.iso '.

  IDE1:0. DeviceType = "cdrom-image".

  IDE1:0.allowGuestConnectionControl = "FALSE".

  ethernet0. Present = 'TRUE '.

  ethernet0.allowGuestConnectionControl = "FALSE".

  ethernet0. Features = "1".

  ethernet0.wakeOnPcktRcv = "FALSE".

  ethernet0.networkName = "Bridged".

  ethernet0. AddressType = 'generated '.

  guestOS = "rhel3.

  UUID. Location = "56 4 d 58 36 3 c 3F 0c 7 a - 96 cd 07 d5 b1 a8 e1 e0.

  UUID. BIOS = "56 4 d 58 36 3 c 3F 0c 7 a - 96 cd 07 d5 b1 a8 e1 e0.

  VC. UUID = "52 88 6f 19 b2 66 ae 20-28 5 c 6 b 8 b 96 a1 15 6 d.

  scsi0:1.present = 'TRUE '.

  scsi0:1.filename = "colossus2_2new.vmdk".

  scsi0:1.writeThrough = 'TRUE '.

  scsi0:2.present = 'TRUE '.

  scsi0:2.filename = "colossus2_3new.vmdk".

  scsi0:2.writeThrough = 'TRUE '.

  scsi0:3.present = 'TRUE '.

  scsi0:3.filename = "colossus2_4new.vmdk".

  scsi0:3.writeThrough = 'TRUE '.

  scsi0:4.present = 'TRUE '.

  scsi0:4.filename = "colossus2_5new - 000001.vmdk".

  scsi0:4.writeThrough = 'TRUE '.

  IDE1:0.startConnected = 'TRUE '.

  IDE1:0.clientDevice = "FALSE".

  ethernet0.generatedAddress = "00: 0C: 29:b1:a8:e1.

  tools.syncTime = "TRUE".

  scsi0:0. Redo = «»

  scsi0:1.redo = «»

  scsi0:2.redo = «»

  scsi0:3.redo = «»

  scsi0:4.redo = «»

  vmotion.checkpointFBSize = "16777216.

  pciBridge0.pciSlotNumber = "17".

  pciBridge4.pciSlotNumber = "21".

  pciBridge5.pciSlotNumber = "22".

  pciBridge6.pciSlotNumber = "23".

  pciBridge7.pciSlotNumber = "24".

  scsi0.pciSlotNumber = "16".

  ethernet0.pciSlotNumber = "32".

  vmci0.pciSlotNumber = "33".

  ethernet0.generatedAddressOffset = '0 '.

  vmci0.ID = "-709777183".

  sched.mem.pshare.Enable = "FALSE".

  mainMem.useNamedFile = "FALSE".

  MemTrimRate = '0 '.

  MemAllowAutoScaleDown = "FALSE".

  Could someone point me to a solution if there is? I have Saturday night here and I would not spend my Sunday to rebuild the server from scratch and have to explain Monday morning I lost 2 months of work for users little by relying on this virtual machine.

  Thank you very much in advance!

  bugjargal,

  In the past if I had a VM that is displayed as invalid when you try to add it to the inventory, I usually just created a new virtual machine based on the original settings & attached the existing VMDK.  Not sure how that will work with a virtual machine that has snapshots, but can be worth (nothing to lose)?

  Doug.

• invalid argument on disks after crash san vmdk... need help urgent

  Hello

  Last night we had an accident SAN because of a power failure. all the vm does not start after this crash.

  We receive the error: Invalid Argument

  also, when I want to delete the pagefile for the most important machine:

  RM: cannot remove 'SBS2008 - 84765360.vswp': invalid argument

  It seems that all of the swap and flat files are locked... I already tried:

  -Restart all esx hosts

  -restart services / services to stop when you try to delete the swap file

  -J' tried to re-create the vmdk file and include the flat file again, no luck

  -move the action to another logical unit number gives me the same error. It does not move

  -copy of the scp of the machine action will not work, cannot access the file.

  -the flat vmdk file renaming works, but I still can't access the file

  -vmware migrate action even error.

  I really need this virtual machine to work, please help

  Kind regards

  Marco Broeken

  Ok.  Here's what I would do: (it worked for me on ESX 3.5 U2)

  • Unregister the virtual machine in the LUN of your ESX 3.5

  • Present the LUN for a version of the host ESX 3.0.2

  • Save a VM from ESX 3.0.2 host

  • Turn on the virtual machine under ESX 3.0.2 and select keep to keep the same UUID

  • Wait for the virtual machine is fully started, stop the virtual machine peacefully

  • Unregister the virtual of ESX 3.0.2 machine

  • Register the virtual machine on ESX 3.5

  • Turn on the virtual machine

  • America Bess God and God bless you too!

  I would like to know if it works.

• error message when try to sync the iPhone, "invalid response from the device?

  What can I do when I receive this error message when you try to sync to my iPhone 5 s - "invalid response from the device?

  -What are your 5 updating to 10.0.2 iOS iPhone? If this is the case, you must have the latest version of iTunes on your computer, which is required for Mac OS X 10.9.5 12.5.1, or above. To meet these specifications will be receiving this error.

• iPad does not connect due to an invalid response?

  I just updated my iPad air to 10.0.2 and received this:

  ITunes could not connect to the ipad "iPad", because an invalid response was received from the device.  Aide said it's a problem of USB, it's using the same exact cable I was using all night with her, and I even tried 2 other new cables with the same result.  Rebooted computer and iPad, the same thing.  It was working fine until I upgraded to, but I have updated to ios 8.4 directly to 10.0.2 and I really want to go back if possible.

  Thank you all in advance...

  Hello. You need iTunes 12.5.1 to support iOS 10.

• iTunes invalid response from the device

  Thus, since updating my iPhone 6 to IOS10, I have been unable to sync with my mac. When I plug my phone I get the message of athis on my mac...

  iTunes could not connect to the iPhone "iPhone", because an invalid response was received from the device.

  I click OK

  I look at my phone it asks if I want to trust this computer. I click Yes. Nothing.

  So I wait. Nothing. I disconnect and try again. Same thing. I tried all the USB ports on my mac. Same thing.

  Search the forums here, looks like a common phenomenon when connecting to a PC, but not a mac.

  Connection to a Mac Pro Tower

  10.7.5

  iPhone 6

  Devices running iOS 10 require the latest version of iTunes, which requires OS X 10.9.5 or more. It's time to upgrade.

• is itunes error message cannot connect to my iphone because of an invalid response was received from the device

  get error message that IOS 10 unable to connect to my iphone iTunes 6 because of an invalid response was received from the device

  Make sure you are using iTunes 12.5.1 or later, as it is required to communicate to iOS 10.

  If iTunes does not recognize your iPhone, iPad or iPod - Apple Support

• IPhone will not connect to iTunes - "invalid response received from the device."

  After years of work very well, I went to put some new music on my phone and all of a sudden got this message "iTunes could not connect to the iPhone 'IPhone of David Platts' because an invalid response was received from the device."?

  I've tried different USB ports, different cables (some Apple official, some after market) and several reboots, but nothing works.

  I'm 10.7.5 OSX and IOS 10 phone you.

  Thanks for the help.

  You have a problem.

  It is good that you have told us you're OS x 10.7.5 (current is MacOS 10.12), because it is your problem.

  iOS 10 requires iTunes 12.5.1 or later to communicate.  iTunes 12.5.1 requres OS X 10.9.5 or later version.

  It's (time to upgrade the operating system of your Mac spent).

  macOS - official Apple Support

• Application failure: invalid statement 4

  After upgrading to Mac OS Sierra, I get "4 the invalid statement" when running applications that worked on El Capitan (on MacBook Pro 2015). Different pages from 2009 indicate that the executable file runs a statement of unknown or not CPU supported. Other items show the incorrect return values. How is it possible for applications that work on the same machine under El Capitan?

  Y at - it new security / firewall app from Sierra which could cause this? Anyone else seeing this?

  Quote including "BREW" applications and programming tools (Haskell, cabal, maven)

  Have you checked to see if there are any available updates for applications that are giving you problems?