DISM /cleanup-image /StartComponentCleanup /ResetBase failed on offline image due to pending operation - windows-10

I tried to customize my own Windows 10 21H2 wim file, I removed some features and added .net 3.5 into the image, no any other updates or packages is added. The image is mount from a wim file to the directory C:\TESTWIN and therefore it is and offline image.
When I tried to run the command DISM /image:C:\TESTWIN /cleanup-image /StartComponentCleanup /ResetBase I got the error 0x800f0806 which said I have a pending operation.
I found that the .Net3.5 component is pending to be install, also the features I removed is pending.
I also did the dism.exe /unmount-wim /mountdir:C:\TESTWIN /commit, but next time when I remount the wim, those pending operation still presist. I have no idea of what to do next, I have read through the documentation of DISM but nothing said about how to deal with pending operation.
Does anyone knows how do I finish/complete those pending operations? That is an offline image so sfc /scannow will not work.

Related

AVD not booting after Android Studio update

My AVDs are no longer booting after I installed a 921MB update released these days. I don't exactly remember the entity of the update (maybe API/SDK revision), I'm using Android Studio 2.3 build AI-162.4069837 with API 25 revision 3 (I think this last thing is the actual update) on Debian.
When I start up the AVD it just keeps a black screen and never completes booting. The log shows this error just after it starts booting the AVD:
1292-1328/? E/vold: Failed to chmod /data/system_ce/0: No such file or directory
1292-1328/? E/vold: Failed to chmod /data/misc_ce/0: No such file or directory
1292-1328/? E/vold: Failed to chmod /data/media/0: No such file or directory
It's like there is no file system initalized.
After that I keep getting a loop of errors, which I pasted at https://pastebin.com/cbk9T8KR.
Anybody else having troubles? Any ideas on how to get the VM working again?
I eventually found a temporary solution hoping they'll fix the bug. You should open config.ini inside .android/AVD/[AVD name]/ and set
hw.gpu.enabled=yes
hw.gpu.mode=swiftshader
and the VM got back to work properly.
Source: https://issuetracker.google.com/issues/36905888
for all Windows Users the config.ini is in
C:\Users\yourname.android\avd\yourdevicename.avd/config.ini
and the entries
hw.gpu.enabled=yes
hw.gpu.mode=auto
exist already. But the change of hw.gpu.mode to "swiftshader" works perfectly.

Kapow ManagementConsole could not start

An error message pops out when I try to connect to the management console. The version is Kapow 10.1.0 master nightly 2370 x64.
The Error message is:
Unable to register to the default cluster: ManagementConsole failed to start: Spring subsystem failed to load.. Retrying
I had to delete the folder on Kapow Appdata User Profile folder, for example:
C:\users\<user>\appdata\local\Kapow
And then restart the RoboServer/Management Console.
This will create a new configuration and from there you can continue the installation (bring up the management console, enter the license, etc)
Please Delete Appdata and open localhost:50080 Management console and delete and then add Cluster settings again.
Now restart the Design studio and open it up again. Make sure you are using same objectdb.
You only need to rename the folder:
C:\Users\<user>\AppData\Local\Kapow\10.ur.version\Data
Then rerun the Management console as Administrator.
If you are still facing the same issue, please uninstall Kapow and install it again (also make sure you renamed the Data folder).

Unable to open Instruments after repeatedly seeing (RunLoop::Xcrun::TimeoutError) error

I've posted this issue
but believe I'm now running into a new one. We have automated tests that run every 15 minutes on a Jenkins server. While I'm still seeing the run_loop error listed in the link above, approximately once per hour I'm now seeing the following error in the console's output
Xcrun timed out after 3.64 seconds executing
xcrun instruments -s templates
with a timeout of 30
(RunLoop::Xcrun::TimeoutError)
When I see this and try to open Instruments, it says "Instruments cannot be opened at this time" and the only solution I've found so far is to reboot the server. This is problematic because there are several jobs running on this server at once and rebooting the machine every hour is not ideal. After rebooting the machine, Instruments is able to be opened and the tests run successfully for about another hour.
I can provide any further information necessary, just not sure where to go from here since I don't see much about this issue online.
Edit: My apologies, the missing information is
Xcode: 7.1.1
MacOS: 10.10.5
Calabash-Cucumber: 0.17.0
I have experienced this as well on our Jenkins CI machine running El Cap and Xcode 7.2. The CoreSimulator and instruments environment becomes unstable rather quickly.
Before running your tests, try:
# From Ruby
RunLoop::CoreSimulator.terminate_core_simulator_processes
# From the command line
$ bundle exec run-loop simctl manage-processes

Cygwin Installation Hangs - man-db

I am trying to Install Cygwin 64 bit on a Windows 2012R2 (64 bit).
Downloading and initial setup went through but when it reached man-db (/etc/postinstall/man-db) the setup hangs
and remains so forever. I waited more than 1.5 Hours but still no progress.
I checked log file in /var/log/setup.log which has following contents.
Updating index cache for path `/usr/share/man/man1'. Wait...
Processing manual pages under /usr/share/man...
/usr/bin/mandb: warning: /usr/share/man/man1/col.1.gz: whatis parse for col(1) failed
/usr/bin/mandb: warning: /usr/share/man/man1/imv.1 is a dangling symlink
/usr/bin/mandb: iconv_open ("UTF-8//IGNORE", "utf8"): Invalid argument
/usr/bin/mandb: warning: /usr/share/man/man1/mc.1.gz: whatis parse for mc(1) failed
I am not sure if I should cancel and start again. Will this setup come out of this stage with at least some error?
Did anyone install 64 bit Cygwin and got this error ?
Please help
Happens to me often. I was setting up 8 servers this week and it happened to 3 of them. Waited many hours and it is still would not finish. Sometimes the re-installation works, some it does not. So I have resorted to kill the mandb.exe process and that allows the installer to finish normally. So far I have found no side effects of doing so.
After waiting for more than 3 hours, I decided to cancel the setup. Then I tried a reinstall, following the steps exactly as in the first install. I did not add or remove any packages. The already selected packages in the first attempt were recognized as installed. This time, the setup stopped at the above step (man-db) briefly and then completed the installation. No errors. So, re-installation solved my problem.
Late to the party, but —
When mandb.exe hung, I killed its parent bash.exe via Task Manager and the installation completed.
I then killed mandb.exe in Task Manager, since it was still running.
I then opened a Cygwin shell and ran mandb -cds. -c recreates the index, -d prints messages (so you can actually tell it's doing something constructive!) and -s suppresses checking for orphaned formatted manual pages ("stray cats").
As I write this, mandb is still chugging along, three or four hours later, with plenty yet to go.
So I'll remember to file a bug report later :) , I did notice one oddity during the mandb run:
mandb: /usr/share/man/man3/jN.3 is self referencing
mandb: warning: /usr/share/man/man3/jnf.3.gz: bad symlink or ROFF `.so' request
I've been struggling with the same problem today until I realised that moving the main Cygwin setup window revealed a popup complaining about "can't open (null) for reading: no such file"
This happens multiple times in a (re)install

NSIS script help-install without killing explorer

When I tried to un-install and install an executable foo.exe, Im geting the below error
Error opening file for writing
click abort to stop the installation
I could find that some files were failed to get deleted while un-installation.
And by using process explorer I can see that explorer.exe has still reference to some dlls of foo.exe even after unregistering them.
and killing the explorer.exe and re-start it again while un-installation solves the issue. (thru NSIS installation script).
or by setting rebook ok flag in script and ask user to re-start his machine before installing foo.exe again.
I don't think its a good solution to ask user to reboot his machine after un-installation .
Can anyone help me on how can I make sure that my installation goes fine instead of restarting explorer.exe
For registered shell extensions there is really no clean way to delete the dll's other than forcing a reboot (Or log-off if they are registered in HKCU\Software\Classes)
If that is not good enough you basically have two options:
Rename the .dll and delete it later
<HACKALERT>Inject a thread that calls CoFreeUnusedLibraries() into every process that has your dll loaded</HACKALERT>
Just killing and restarting explorer is not really an option since you don't know if some other program is also using your shell extension.

Resources