We could not copy the content to the Clipboard, it is in use by another application. You can still paste your content within this workbook but it will not be available in other applications.

Anonymous
2022-05-18T13:29:01+00:00

Win 10 version 21H2 Build 19044.1706

Excel 2016 Version 2204 Build 15128.20224

This problem occurs randomly and with only a few cells being copied. The spreadsheet locks up and the only way out is Save>Close and open the book again. Sometimes that doesn't work and I have to close Excel completely.

Sometimes the top ribbon completely greys out and I can't do anything.

This is becoming a significant problem.

Microsoft 365 and Office | Excel | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

111 answers

Sort by: Newest
  1. Anonymous
    2022-12-18T16:48:14+00:00

    You don't seem to know what mitigate means.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2022-12-13T15:13:25+00:00

    I was wrong, the problem has not disappeared. Returned as annoying as ever.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-12-11T22:42:53+00:00

    Has anyone tried the solution I posted 10th August? If so, does it work?

    Simply add these two directories to your system:

    C:\Windows\System32\config\systemprofile\Desktop

    C:\Windows\SysWOW64\config\systemprofile\Desktop

    I already had one of them. The original poster then sugested removing them but I haven't and the problem has gone.

    I have run Office 2019 on Windows 10 on my laptop and have used Excel 2019 for the past year. The problem described in these posts appeared after a year's usage of Excel in the last few days. I had the same problem with Excel 2016 on my PC running Windows 8.1 and currently without a working power supply.

    As mentioned above both folders

    C:\Windows\System32\config\systemprofile\

    C:\Windows\SysWOW64\config\systemprofile\

    already contained one sub-folder named AppData which in turn each had a number of sub-folders. So I added the sub-folder Desktop to each of the above named folders and after half an hours usage of Excel the problem seems to have disappeared. So far so good.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-12-08T14:54:21+00:00

    Due to features change often I often run a file that I copied from a helpful note.

    I created a batch file and run it in administrator mode. It replaces corrupt or broken files.

    I have had no problems with this code.

    However, provide for recovery, if needed. This is "as is".

    Perhaps try one command at a time.

    aja.bat

    @echo off
    date /t & time /t
    echo Dism /Online /Cleanup-Image /StartComponentCleanup
    Dism /Online /Cleanup-Image /StartComponentCleanup
    echo ...
    date /t & time /t
    echo Dism /Online /Cleanup-Image /RestoreHealth
    Dism /Online /Cleanup-Image /RestoreHealth
    echo ...
    date /t & time /t
    echo SFC /scannow
    SFC /scannow
    date /t & time /t
    pause

    ======

    (end of batch file)

    Platform

    Device name xxxxxxxx
    Processor 11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz 2.50 GHz
    Installed RAM 16.0 GB (15.6 GB usable)
    System type 64-bit operating system, x64-based processor

    Edition Windows 10 Pro
    Version 22H2
    Installed on ‎1/‎3/‎2022
    OS build 19045.2251
    Experience Windows Feature Experience Pack 120.2212.4180.0

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-12-07T18:07:59+00:00

    I have found that "Runtime Broker" is locked in a "deadly embrace" with another "Runtime Broker" .

    Deadlock (which is sometimes called the deadly embrace) is another crippling condition. It occurs when two or more programs are each waiting for the others to complete - or even just to produce a data value - before proceeding.

    Best solution is Microsoft solve this many year hic-up; eliminating the "deadly embrace"

    Instead, I use task Manager and find the closest "Runtime Broker" process to the "S"'s.

    I delete this "Runtime Broker" and any child processes if it exists.

    Check if problem went away. If not, repeat and delete the next (last ) "Runtime Broker" .

    Worse reboot. It is gone.

    Not professional;but works for my platform Win 10, MSA 360 and stuff.

    That is all I have. Good Luck.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments