iPhone can't transfer Photos to Windows 11

1. REBOOT your iPHONE - seriously.

2. Unplug, the replug iPhone into PC.

3. If no DCIM folder in iPHONE device, take a new picture - seriously.

4. Close "This PC", then re-open it, then click on iPhone again.

5. Wait a few minutes while it is connected for "Internal Storage" folder to appear

6. Turn off Passcodes completely.

7. Turn Autolock off (to Never).

8. Make sure phone is unlocked.

9. Try a different PC.

10. Stop Using iPhones and get an Android.

You want to clear up some space on your iPhone:

In DCIM, you can't delete directories, but go inside each DCIM folder, select the files you want to delete, and delete them there.

Sites added to this zone must use the prefix https

Issue:When trying to add a https website to a Internet Security Zone, the error "Sites added to this zone must use the prefix https:" appears.
Environment:
Internet Explorer on Windows
Symptoms:
Typically, this happens when the website does not have a https prefix, however, sometimes this error can occur when the website being added does have an https prefix!
Solution:
This was occurring on a system with a seemingly unrelated setting.
Using administrative rights:
Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Internet Explorer
Find the setting "Security Zones: Use only machine settings"
If this is Disabled or Not Configured, try changing this to Enabled.
Close the Internet Explorer browser.
Run "gpupdate /force"
Restart Internet Explorer and try again.

Unable to read from or write to the database

Issue:
When attempting to use secedit to analyze a database (sdb file), you receive the following information - Unable to read from or write to the database
Environment:
Windows
Solution:
Although it is worth checking permissions on the sdb file, the issue was occurring because the read-only attribute was assigned on the file. Clear the bit, and try again.

ACAS \ Nessus Causes Systems to Crash, Reboot, or BSOD upon Credentialed Scans

Issue:
ACAS \ Nessus Causes Systems to Crash, Reboot, or BSOD upon Credentialed Scans
Environment:
Windows 7 workstations
Symptoms:
The moment an ACAS \ Nessus Credentialed scan begins, the target system crashes, reboots, or BSODs.
Solution:
Tracked this down to Microsoft Patch 3161531.
Appears to be happening when Tenable accesses C$ (almost immediately upon scan).
A related discussion on BSOD's when accessing C$ is here:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/4b1e0e7b-3b26-41f3-8979-0cd7a25d9209/kb3161561-crashing-server-when-remotly-accessed-with-smb?forum=winservergen
It appears that Microsoft has put out a related hotfix to this issue. Not because of Nessus specifically, but due to general problems when accessing C$, which I believe is ultimately why Nessus is failing.
For details, see both:
https://support.microsoft.com/en-us/kb/3161561
https://support.microsoft.com/en-us/kb/3179573

Updates not working on new install of Windows 7

Issue:
Updates not working on new install of Windows 7
Environment:
Windows 7 x64 Fresh Install
Symptoms:
Going to Windows Updates results in a window which states 'Checking for updates', but that check never ends.
Solution:
I did see this solution after much looking on answers.microsoft.com , but wanted to put it here as it specifically worked for me:
Install Windows 7.
Don't connect to internet.
Install Windows6.1-KB3083710-x64.msu.
Reboot.
Install Windows6.1-KB3102810-x64.msu
Reboot.
Use the Windows Update tool as normal. The initial check for updates may still take some time, but should eventually work.

If you want to have a task deleted automatically after it runs, you must add at least one trigger that has an expiration date.

Issue:
When attempting to use Task Scheduler with the "/sc onstart" and "/z" switches, the task does not get deleted. The error "If you want to have a task deleted automatically after it runs, you must add at least one trigger that has an expiration date." may occur. This occurs when trying to run a scheduled task on startup (onstart) and have it deleted upon completion (/z). Although a deletion of the task could be performed via the GUI, the point is to have the task removed automatically.
Environment:
Windows. The goal is to kickoff a task when a computer is rebooted, have the task complete and then be deleted so that it doesn't run a second time.
Symptoms:
Task runs, however does not get deleted upon completion.
Solution:
It appears that to use the "/sc once" switch, a time MUST be entered. Without knowing the time that the system will be rebooted, this isn't easy or practical to do. Using the "/sc onstart" option with "/z" doesn't produce the desired results either (as mentioned above). The solution was to have the task delete itself.
The first task can be created such as:
SCHTASKS /create /sc onstart /tn "myTask" /tr "C:\temp\test.bat" /ru SYSTEM
The test.bat file would accomplish whichever tasks were desired, and then delete the task:
test.bat:
****
...Actions to take...
SCHTASKS /delete /tn "myTask" /f
****

Please note that this issue is different from the error "The task XML is missing a required element or attribute" which occurs if not using the /v1 switch, as described here:
https://support.microsoft.com/en-us/kb/2004151

The uploaded content exceeded the maximum size allowed

Issue:
When attempting to upload a software package into the an ePO master repository, an error occurs: "The uploaded content exceeded the maximum size allowed"
Environment:
Web Interface of McAfee ePolicyOrchestrator (ePO)
Symptoms:
Hard disk space is not lacking, and yet, shortly after trying to upload the ZIP file package, the error occurs.
Solution:
Although this could very well be traced to a corrupt zip file, the problem was that the ZIP file I was using contained a tar.gz file inside. I had to extract the zip file, then extract the tar.gz (use a program such as 7zip). Once that was extracted, there was another ZIP file which was the appropriate one to use.

Error untaring Plugins (rc = 2)

Issue:
When attempting to update plugins (such as Active plugins) into Tenable SecurityCenter, an error is received such as: "Error untaring Plugins (rc = 2)"
Environment:
Web Interface of Tenable SecurityCenter hosted on RedHat
Symptoms:
Plugins may or may not appear to be working for a moment, however they quickly fail. An error message indicates: "Error untaring Plugins (rc = 2)".
Solution:
Although this could very well be traced to a corrupt tar.gz file (in which case, re-download and try again), the solution in this case was to free up some hard disk space. Logging into the Redhat SecurityCenter installation, I noted that although the plugins are roughly 150MB, when untarred and gz'ed, they expand to a size requiring up to 900MB. If there is anything less than 1GB free on the root (/) partition, some of it should be moved or removed.

Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again.

Issue: 
Connecting to another system with RDP fails. This system may successfully be able to handle RDP requests from other devices. This occured in a Windows RDP Client connecting to a Redhat XRDP Service.
Environment:
Windows workstation connecting to Redhat via XRDP.
Symptoms:
Connection appears to begin, but error message "Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again." appears.
Solution:
Although the following article may be helpful:
https://support.microsoft.com/en-us/kb/329896
The solution in this case was to disable the enforcement of FIPS. One method is to set the following value to 0:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy

Recording Tab Missing on DVD CD RW Properties

Issue: 
When attempting to burn a CD or DVD with Windows built-in burning features, the option is not available.
Environment:
Windows 7 Non-Domain System. Although solution could be applied to a domain environment. This occurred on a Dell laptop.
Symptoms:
The tell-tale sign that Windows will not be able to record to disk is a missing recording tab of the DVD RW properties.
Solution:
For many people, this issue issue is caused by a local security policy found here:
User Configuration\Administrative Templates\Windows Components\Windows Explorer
"Remove CD Burning Features" set to Enabled will remove CD Burning.
However, this was not the case for my system;
In my policy editor:
Computer Configuration\Administrative Templates\System\Removable Storage Access\
"CD and DVD: Deny write Access" set to Enabled will remove CD Burning.
Change the setting from Enabled to Disabled. This setting can be editied by double-clicking on the item.
Click the "OK" button at the bottom of the window.
Close the window titled "Local Group Policy Editor"

Check if CD burning is working. If yes, great! Mine was not. No, I had to also uninstall and reinstall the driver for this to work!

Click on "Start" button
Type in "Device Manager"
Click on Device Manager in search results.
If prompted to allow "Microsoft Management Console" to make changes to your computer, Click "Yes".
Expand DVD/CD-ROM drives
Double-Click on drive (ex: Matshita DVD+RW)
Click on "Driver" tab
Click "Uninstall" button
Accept the warning that the device is about to be uninstalled by Clicking "OK"
While still in device manager, Click on the "Action" menu from the top bar.
Select "Scan for Hardware Changes"
The DVD+RW will automatically reinstall.

Check if CD burning is working. If not, Reboot.

Note: To open policy editor:

Click on "Start\Windows" button
Enter gpedit.msc and Press Enter
If prompted to allow "Microsoft Management Console" to make changes to your computer, Click "Yes".

Your account is configured to prevent you from using this computer. Please try another computer.

Issue:
When attempting to log on to a Windows system, the error message: "Your account is configured to prevent you from using this computer. Please try another computer." is received. The system then returns to a logon screen.
Environment:
Windows workstation. Non-Administrator account login.
Symptoms:
An administrator account appears to be able to log into a target system, but "standard" users cannot. The standard account is not locked.
Solution:
There was a corrupt entry in the registry for the item: "HKLM\System\CurrentControlSet\Control\LSA\CrashOnAuditFail" This should be a DWORD of 0 or 1 only. I recommend 0. Unsure as to the root cause of the corruption. Review the system's event logs. This issue is likely to take effect if the logs are full, thus impacting the ability to perform "audits".
It is worth reviewing all of the system logs and clearing them off.
Even after doing all this, the issue may still remain. It may take a reboot or a little bit of time before the system will allow for a login, especially if the computer is "slow".
Note:
If the solution provided does not resolve the issue, the following may help:
In ADUC on a domain environment, the account may be limited as to which systems it is allowed to "Log On To..."
The login hours of the account may be impacting the abillity to login.

Detecting MSXML4, MSXML6 Versions

Issue:
Service Pack of MSXML is not apparent. For example, the Add\Remove Programs applet may list MSXML6 Parser as an installed program, without mention that it is Service Pack 2.
Environment:
Windows All Versions
Solution:
Look at the version of the %systemfiles%\msxml*.dll
The number which follows the major version is the "Service Pack"
For example, if on the properties of msxml6.dll, the version is 6.2, then the Service Pack is 2.

Project: Detect MSXML Service Pack from Command Line
Obtain the latest version of "filever.exe", available for free from Microsoft as part of the Windows Support Tools. For example, from http://www.microsoft.com/en-us/download/details.aspx?id=18546
Then, run the following:

filever.exe C:\Windows\System32\msxml* > xmlversions.txt
findstr /C:"  4.0" xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML4)
findstr /C:"  4.1" xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML4SP1)
findstr /C:"  4.2" xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML4SP2)
findstr /C:"  4.3" xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML4SP3)
findstr /C:"  6.0" C:\Temp\xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML6)
findstr /C:"  6.1" C:\Temp\xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML6SP1)
findstr /C:"  6.2" C:\Temp\xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML6SP2)
findstr /C:"  6.3" C:\Temp\xmlversions.txt > nul
IF %ERRORLEVEL% EQU 0 (ECHO MSXML6SP3)

Symantec Endpoint Protection Client Rolls Back During Installation

Issue:
Symantec Endpoint Protection Client Rolls Back During Installation
Environment:
Windows client (XP) in need of an Endpoint Protection Client in a domain with Symantec Endpoint Protection Server and other working Symantec Clients
Symptoms:
Product initially appears to be installing fine. Near the end of installation, the progress bar rolls back and the installation fails.
Solution:
I've encountered this issue a few times... Try the following in order of most to least likely:
1. Verify you are logged in as Administrator
2. If user permissions are misconfigured, try using a different Administrator account to perform the installation. For example, use the local system administrator account, or a newly created administrator account, or your backup administrator account. If this fixes your issue, you should track down why your administrator account is limited where your other accounts are not.
3. Perform a cleanup of Symantec Applications on the client:
A. Run Cleanwipe (Symantec's Installation Cleanup tool), Reboot, then try reinstalling. Select "yes" to each Cleanwipe option (Skip if cleanwipe not available)
B. Verify in Add\Remove Programs that both Liveupdate and the Client are removed.
C. Use a registry analyzer to clean Symantec References (ccleaner, for example)
D. Reboot, then reinstall the client
4. Verify that the latest root certs are on the system (obtaining from Microsoft is OK)
5. Use the Symantec Support Tool (available from the Server installation media) and run on target machine. Address any issues which this tool finds.
The following steps have not worked for me, but have come up in my research:
6. Install the latest version of Windows Installer
7. Install Liveupdate (LUSETUP.exe) before installing the client on target machine.
8. In the registry (Obligatory Warning: Backup registry before modifying it!),
Find:
HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\AppData
value=%APPDATA%
and change it to value=%USERPROFILE%\AppData\Roaming
9. Update Internet Explorer 6 to Internet Explorer 7
10. Perform a thorough registry check for Symantec, and be sure to remove:
HKEY_USERS\.DEFAULT\Software\Symantec [remove]
HKEY_CURRENT_USER \Software\Symantec
11. On the server, rebuild the client package and redeploy or re-run on target system
12. Verify that the correct version of the client is being installed (32bit, 64bit, etc.)
13. Click on Start, Select Run, Type: "dcomcnfg", Expand the Component Services, Expand Computers, Expand My Computer, Expand DCOM Config, Right-click LuComServer and select Properties, Click on Identity tab, Select the "This user" option and choose a Local Administrator account., Click OK, Restart the computer

Login Banner for Redhat 6 (RHEL6) Issues

Issue:
Problems occur after lengthy log-in banner is added
Environment:
Redhat 6 with Gnome Login Environment
Solution:
First, let's enable the banner:

gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory/ --type boolean --set /apps/gdm/simple-greeter/banner_message_enable 1

Second, let's add the banner's full text (no returns):
gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory/ --type string --set /apps/gdm/simple-greeter/banner_message_text "YOURBANNERHERE"

Problem 1: No return lines 
First, navigate to the file which contains the banner, %gconf.xml
cd /etc/gconf/gconf.xml.mandatory/apps/gdm/simple-greeter/

Second, modify the file. Locate the banner text and add returns as needed.

Problems 2 and 3: Centered text. Part of the user list is cut off!
First, navigate to the login banner configuration file
cd /usr/share/gdm
Second, backup this file, as modifying it can be very dangerous!
cp gdm-greeter-login-window.ui gdm-greeter-login-window.ui.bak
Third, locate the "auth-banner-label" section in this file and modify/add code in red:

<object class="GtkLabel" id="auth-banner-label">
   <property name="visible">True</property>
   <property name="justify">left</property>
   <property name="wrap">True</property>
</object>
   <packing>
      <property name="expand">False</property>
      <property name="fill">False</property>
      <property name="position">3</property>
   </packing>

CMS Plug-in

Issue:
CMS Plug-in : A supported CMS Plug-in has NOT been installed. CMS will not start until you download the CMS Plug-in on your PC. Click below to download the Plug-in:
Then, you click on the Download button, and get a 404 Error...
Environment:
Accessing an older Cisco 2970 Series switch's website
Solution:
Just ignore the link. All of the features that CMS can do have been rolled into a newer product called Cisco Network Assistant. Download and Run CNA from Cisco's website instead to connect.

Error Copying File: Cannot Copy The specified network name is no longer available

Issue:
Error Copying File: Cannot Copy "filename" The specified network name is no longer available
Environment:
Windows XP client copying to a fileshare in a domain environment
Symptoms:
The failing file was over 1MB. Files under 1MB seemed to copy fine, albeit slowly
Solution:
Replace the faulty switch which was giving my system connectivity to the rest of the network.

Our Linksys SD2008 ver 2.1 switch was to blame. Removal of the cover revealed failed (swelled) capacitors. Apparently, a lot of people have complained about this particular switch, version 2.x. In version 1, there was no problem except for a fan which customers complained was too noisy. Solution? Sell the switch without a fan as version 2 and let it overheat!